Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <rnbrady@gmail.com>) id 1YDISQ-00023t-1e for bitcoin-development@lists.sourceforge.net; Mon, 19 Jan 2015 19:57:54 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.169 as permitted sender) client-ip=209.85.214.169; envelope-from=rnbrady@gmail.com; helo=mail-ob0-f169.google.com; Received: from mail-ob0-f169.google.com ([209.85.214.169]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YDISP-000789-BM for bitcoin-development@lists.sourceforge.net; Mon, 19 Jan 2015 19:57:54 +0000 Received: by mail-ob0-f169.google.com with SMTP id va8so6570472obc.0 for <bitcoin-development@lists.sourceforge.net>; Mon, 19 Jan 2015 11:57:48 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.60.141.231 with SMTP id rr7mr1159311oeb.19.1421697467950; Mon, 19 Jan 2015 11:57:47 -0800 (PST) Received: by 10.76.153.164 with HTTP; Mon, 19 Jan 2015 11:57:47 -0800 (PST) In-Reply-To: <2C7D6208-1921-4DDC-90FE-DB1ABE1D61DB@petertodd.org> References: <CAN5esQJe0uUm0NyctaBa6WH7_JjeE_OLR=FY_XQWnSr50VRDyA@mail.gmail.com> <CAJHLa0OTynX4oiQoyanpRKE2tpAuS4L5X-2j20328725J9RrvQ@mail.gmail.com> <2C7D6208-1921-4DDC-90FE-DB1ABE1D61DB@petertodd.org> Date: Mon, 19 Jan 2015 19:57:47 +0000 Message-ID: <CAN5esQLCV=L0kYxDGhK2F=qZ8OqMxyYS+-Pn17U_M+nV4Sj3Og@mail.gmail.com> From: Richard Brady <rnbrady@gmail.com> To: Peter Todd <pete@petertodd.org> Content-Type: multipart/alternative; boundary=047d7b339a3f8e2d3b050d06bc03 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (rnbrady[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1YDISP-000789-BM Cc: Bitcoin <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] BIP70: why Google Protocol Buffers for encoding? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Mon, 19 Jan 2015 19:57:54 -0000 --047d7b339a3f8e2d3b050d06bc03 Content-Type: text/plain; charset=UTF-8 Thanks guys, great answers. The design choice certainly makes a lot more sense now regardless of whether one agrees with it or not. Regards, Richard --047d7b339a3f8e2d3b050d06bc03 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat= ure">Thanks guys, great answers.=C2=A0</div><div class=3D"gmail_signature">= <br></div><div class=3D"gmail_signature">The design choice certainly makes = a lot more sense now regardless of whether one agrees with it or not.</div>= </div><div class=3D"gmail_signature"><br></div><div class=3D"gmail_signatur= e">Regards,</div><div class=3D"gmail_signature">Richard</div> <br></div></div> --047d7b339a3f8e2d3b050d06bc03--