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