Message-ID: <526DD18A.7060201@jerviss.org>
Date: Sun, 27 Oct 2013 21:52:58 -0500
From: kjj <bitcoin-devel@jerviss.org>
User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64;
	rv:24.0) Gecko/20100101 SeaMonkey/2.21
MIME-Version: 1.0
To: Gavin Andresen <gavinandresen@gmail.com>
References: <274a1888-276c-4aa6-a818-68f548fbe0fa@me.com>	<9DCDB8F6-E3B2-426B-A41E-087E66B3821A@gmail.com>	<526B45DB.2030200@jerviss.org>
	<CABsx9T2OMA_u=S9yUh2j78QDuCDUorYctktuixjwAjqc6neW=Q@mail.gmail.com>
In-Reply-To: <CABsx9T2OMA_u=S9yUh2j78QDuCDUorYctktuixjwAjqc6neW=Q@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------050804060402000507010002"
Received-SPF: pass (inana.jerviss.org: 192.151.168.109 is authenticated by a
	trusted mechanism)
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Feedback requested: "reject" p2p message
Precedence: list

This is a multi-part message in MIME format.
--------------050804060402000507010002
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Any reason not to use actual HTTP codes?  I'm not aware of any major 
deficiency in them.  Most of them won't apply to us, which is fine, they 
don't seem to apply to HTTP either.  We can extend the scheme on our own 
if we find a good reason to.

That implies 16 bits, or a varint.  I would avoid a string or varstring 
here; we already have a text field.  Varint vs. 16 bits is a minor 
issue, and arguments can be made in both directions.  I flipped a coin 
and got heads, so I'll say varint.

Gavin Andresen wrote:
> RE: use HTTP-like status codes:
>
> Okey dokey, I'll add a one-byte machine-readable HTTP-like status 
> code. Unless y'all want a 32-bit status code.  Or maybe a varint. Or a 
> three-character numeric string. I really and truly don't care, but I 
> am writing this code right now so whatever you want, decide quickly.
>
> If anybody has strong feelings about what the reject categories should 
> be, then please take the time to write a specific list, I can't read 
> your mind....
>
>
> -- 
> --
> Gavin Andresen
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development


--------------050804060402000507010002
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Any reason not to use actual HTTP
      codes?&nbsp; I'm not aware of any major deficiency in them.&nbsp; Most of
      them won't apply to us, which is fine, they don't seem to apply to
      HTTP either.&nbsp; We can extend the scheme on our own if we find a
      good reason to.<br>
      <br>
      That implies 16 bits, or a varint.&nbsp; I would avoid a string or
      varstring here; we already have a text field.&nbsp; Varint vs. 16 bits
      is a minor issue, and arguments can be made in both directions.&nbsp; I
      flipped a coin and got heads, so I'll say varint.<br>
      <br>
      Gavin Andresen wrote:<br>
    </div>
    <blockquote
cite="mid:CABsx9T2OMA_u=S9yUh2j78QDuCDUorYctktuixjwAjqc6neW=Q@mail.gmail.com"
      type="cite">
      <div dir="ltr">RE: use HTTP-like status codes:
        <div><br>
        </div>
        <div>Okey dokey, I'll add a one-byte machine-readable HTTP-like
          status code. Unless y'all want a 32-bit status code. &nbsp;Or maybe
          a varint. Or a three-character numeric string. I really and
          truly don't care, but I am writing this code right now so
          whatever you want, decide quickly.</div>
        <div><br>
        </div>
        <div>If anybody has strong feelings about what the reject
          categories should be, then please take the time to write a
          specific list, I can't read your mind....</div>
        <div class="gmail_extra"><br>
          <br>
          -- <br>
          --<br>
          Gavin Andresen<br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register &gt;
<a class="moz-txt-link-freetext" href="http://pubads.g.doubleclick.net/gampad/clk?id=60135991&amp;iu=/4140/ostg.clktrk">http://pubads.g.doubleclick.net/gampad/clk?id=60135991&amp;iu=/4140/ostg.clktrk</a></pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Bitcoin-development mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050804060402000507010002--