{"type":"rich","version":"1.0","author_name":"npub1t9txg5aevth45pu9hcz075tj3ch25fydn8c38wew90qjjdjv3rqq3r6cf0","author_url":"https://nostr.ae/npub1t9txg5aevth45pu9hcz075tj3ch25fydn8c38wew90qjjdjv3rqq3r6cf0","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-10-28\n📝 Original message:Any reason not to use actual HTTP codes?  I'm not aware of any major \ndeficiency in them.  Most of them won't apply to us, which is fine, they \ndon't seem to apply to HTTP either.  We can extend the scheme on our own \nif we find a good reason to.\n\nThat implies 16 bits, or a varint.  I would avoid a string or varstring \nhere; we already have a text field.  Varint vs. 16 bits is a minor \nissue, and arguments can be made in both directions.  I flipped a coin \nand got heads, so I'll say varint.\n\nGavin Andresen wrote:\n\u003e RE: use HTTP-like status codes:\n\u003e\n\u003e Okey dokey, I'll add a one-byte machine-readable HTTP-like status \n\u003e code. Unless y'all want a 32-bit status code.  Or maybe a varint. Or a \n\u003e three-character numeric string. I really and truly don't care, but I \n\u003e am writing this code right now so whatever you want, decide quickly.\n\u003e\n\u003e If anybody has strong feelings about what the reject categories should \n\u003e be, then please take the time to write a specific list, I can't read \n\u003e your mind....\n\u003e\n\u003e\n\u003e -- \n\u003e --\n\u003e Gavin Andresen\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 Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131027/447ba632/attachment.html\u003e"}