{"type":"rich","version":"1.0","author_name":"npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","author_url":"https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-01-19\n📝 Original message:Text formats such as XML or JSON are far less deterministic, are more\nloosely specified, have wide variance in parsing, are not very hash-able,\nthe list goes on.\n\n\nOn Mon, Jan 19, 2015 at 2:07 PM, Richard Brady \u003crnbrady at gmail.com\u003e wrote:\n\n\u003e Hi Gavin, Mike and co\n\u003e\n\u003e Is there a strong driver behind the choice of Google Protocol Buffers for\n\u003e payment request encoding in BIP-0070?\n\u003e\n\u003e Performance doesn't feel that relevant when you think that:\n\u003e 1. Payment requests are not broadcast, this is a request / response flow,\n\u003e much more akin to a web request.\n\u003e 2. One would be cramming this data into a binary format just so you can\n\u003e then attach it to a no-so-binary format such as HTTP.\n\u003e\n\u003e Some great things about protocols/encodings such as HTTP/JSON/XML are:\n\u003e 1. They are human readable on-the-wire. No Wireshark plugin required,\n\u003e tcpdump or ngrep will do.\n\u003e 2. There are tons of great open source libraries and API for parsing /\n\u003e manipulating / generating.\n\u003e 3. It's really easy to hand-craft a test message for debugging.\n\u003e 4. The standards are much easier to read and write. They don't need to\n\u003e contain code like BIP-0070 currently does and they can contain examples,\n\u003e which BIP70 does not.\n\u003e 5. They are thoroughly specified by independent standards bodies such as\n\u003e the IETF. Gotta love a bit of MUST / SHOULD / MAY in a standard.\n\u003e 6. They're a family ;-)\n\u003e\n\u003e Keen to hear your thoughts on this and very keen to watch the payment\n\u003e protocol grow regardless of encoding choice! My background is SIP / VoIP\n\u003e and I think that could be a fascinating use case for this protocol which\n\u003e I'm hoping to do some work on.\n\u003e\n\u003e Best,\n\u003e Richard\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e New Year. New Location. New Benefits. New Data Center in Ashburn, VA.\n\u003e GigeNET is offering a free month of service with a new server in Ashburn.\n\u003e Choose from 2 high performing configs, both with 100TB of bandwidth.\n\u003e Higher redundancy.Lower latency.Increased capacity.Completely compliant.\n\u003e http://p.sf.net/sfu/gigenet\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\n\u003e\n\n\n-- \nJeff Garzik\nBitcoin core developer and open source evangelist\nBitPay, Inc.      https://bitpay.com/\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150119/2046cd15/attachment.html\u003e"}