From: Andy Parkins <andyparkins@gmail•com>
To: bitcoin-development@lists•sourceforge.net,
Amir Taaki <zgenjix@yahoo•com>
Subject: Re: [Bitcoin-development] BIP language on normative behavior
Date: Wed, 21 Dec 2011 09:27:05 +0000 [thread overview]
Message-ID: <201112210927.11979.andyparkins@gmail.com> (raw)
In-Reply-To: <1324429140.3740.YahooMailNeo@web121001.mail.ne1.yahoo.com>
[-- Attachment #1: Type: Text/Plain, Size: 927 bytes --]
On 2011 December 21 Wednesday, Amir Taaki wrote:
> In the original intention for BIP_0014, that would map to:
>
> /Gecko:20110613/Firefox:6.0a2/Mozilla:5.0/
>
> With something like WebKit, it becomes easy to see why that would be
> useful. You can suddenly do a network wide scan of all browsers using
> WebKit, rather than having to maintain a database of all WebKit enabled
> browsers.
This seems excellent to me.
I think most developers want to do the right thing when it comes to standards,
and it is only the inflexibility or ambiguity of a standard that means they
don't.
This heirarchical method lets every client supply all the information they
have -- nobody has to make a decision to leave something out. The internal
debate they would have "is my gui version more important than my protocol
engine version?" is unnecessary.
Andy
--
Dr Andy Parkins
andyparkins@gmail•com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-12-21 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 22:29 Gregory Maxwell
2011-12-19 22:36 ` [Bitcoin-development] Lying about User Agent (was: BIP language on normative behavior) Luke-Jr
2011-12-21 0:59 ` [Bitcoin-development] BIP language on normative behavior Amir Taaki
[not found] ` <201112202007.49399.luke@dashjr.org>
2011-12-21 1:14 ` Amir Taaki
2011-12-21 9:27 ` Andy Parkins [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201112210927.11979.andyparkins@gmail.com \
--to=andyparkins@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=zgenjix@yahoo$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox