On Tue, Jun 17, 2014 at 10:08 AM, Wladimir <laa...@gmail.com> wrote: > On Tue, Jun 17, 2014 at 10:02 AM, Matt Whitlock <b...@mattwhitlock.name> > wrote: >> On Tuesday, 17 June 2014, at 9:57 am, Wladimir wrote: >>> Yes, as I said in the github topic >>> (https://github.com/bitcoin/bitcoin/pull/4351) I suggest we adapt a >>> string-based name space for extensions. >> >> Why use textual strings? These fields are not for human consumption. Why not >> use UUIDs, which are fixed length and will not waste as much bandwidth in >> the protocol? Or if you'd prefer a hierarchical namespace, you could use >> OIDs, a la ASN.1.
Also it IS useful for these fields to be human readable for statistics, peer list views and such. When encountering a new, unknown extension when connecting to a node it's much more useful to get a google-able string to find out what it is about, than some long hexadecimal or dotted-number identifier. Wladimir ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
