<oembed><type>rich</type><version>1.0</version><author_name>npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7</author_name><author_url>https://nostr.ae/npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2013-10-28&#xA;📝 Original message:HTTP also defines success codes (2xx). Are we also talking about ACK&#xA;messages now, rather than just REJECT messages?&#xA;&#xA;&#xA;On 10/28/2013 03:52 AM, kjj wrote:&#xA;&gt; Any reason not to use actual HTTP codes?  I&#39;m not aware of any major&#xA;&gt; deficiency in them.  Most of them won&#39;t apply to us, which is fine, they&#xA;&gt; don&#39;t seem to apply to HTTP either.  We can extend the scheme on our own&#xA;&gt; if we find a good reason to.&#xA;&gt; &#xA;&gt; That implies 16 bits, or a varint.  I would avoid a string or varstring&#xA;&gt; here; we already have a text field.  Varint vs. 16 bits is a minor&#xA;&gt; issue, and arguments can be made in both directions.  I flipped a coin&#xA;&gt; and got heads, so I&#39;ll say varint.&#xA;&gt; &#xA;&gt; Gavin Andresen wrote:&#xA;&gt;&gt; RE: use HTTP-like status codes:&#xA;&gt;&gt;&#xA;&gt;&gt; Okey dokey, I&#39;ll add a one-byte machine-readable HTTP-like status&#xA;&gt;&gt; code. Unless y&#39;all want a 32-bit status code.  Or maybe a varint. Or a&#xA;&gt;&gt; three-character numeric string. I really and truly don&#39;t care, but I&#xA;&gt;&gt; am writing this code right now so whatever you want, decide quickly.&#xA;&gt;&gt;&#xA;&gt;&gt; If anybody has strong feelings about what the reject categories should&#xA;&gt;&gt; be, then please take the time to write a specific list, I can&#39;t read&#xA;&gt;&gt; your mind....&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt; -- &#xA;&gt;&gt; --&#xA;&gt;&gt; Gavin Andresen&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt; ------------------------------------------------------------------------------&#xA;&gt;&gt; October Webinars: Code for Performance&#xA;&gt;&gt; Free Intel webinars can help you accelerate application performance.&#xA;&gt;&gt; Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from &#xA;&gt;&gt; the latest Intel processors and coprocessors. See abstracts and register &gt;&#xA;&gt;&gt; http://pubads.g.doubleclick.net/gampad/clk?id=60135991&amp;iu=/4140/ostg.clktrk&#xA;&gt;&gt;&#xA;&gt;&gt;&#xA;&gt;&gt; _______________________________________________&#xA;&gt;&gt; Bitcoin-development mailing list&#xA;&gt;&gt; Bitcoin-development at lists.sourceforge.net&#xA;&gt;&gt; https://lists.sourceforge.net/lists/listinfo/bitcoin-development&#xA;&gt; &#xA;&gt; &#xA;&gt; &#xA;&gt; ------------------------------------------------------------------------------&#xA;&gt; October Webinars: Code for Performance&#xA;&gt; Free Intel webinars can help you accelerate application performance.&#xA;&gt; Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from &#xA;&gt; the latest Intel processors and coprocessors. See abstracts and register &gt;&#xA;&gt; http://pubads.g.doubleclick.net/gampad/clk?id=60135991&amp;iu=/4140/ostg.clktrk&#xA;&gt; &#xA;&gt; &#xA;&gt; &#xA;&gt; _______________________________________________&#xA;&gt; Bitcoin-development mailing list&#xA;&gt; Bitcoin-development at lists.sourceforge.net&#xA;&gt; https://lists.sourceforge.net/lists/listinfo/bitcoin-development&#xA;&gt;</html></oembed>