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