References: <1320268981.72296.YahooMailNeo@web121003.mail.ne1.yahoo.com>
	<1320507589.87534.YahooMailNeo@web121019.mail.ne1.yahoo.com>
	<CALxbBHWYdt_LRQE5K=36fXNNSqyGVSyYwxi2-p8mxQaei5LCZg@mail.gmail.com>
	<201111051229.16790.luke@dashjr.org>
Message-ID: <1320511212.70648.YahooMailNeo@web121017.mail.ne1.yahoo.com>
Date: Sat, 5 Nov 2011 09:40:12 -0700 (PDT)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <201111051229.16790.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="-71337780-990759556-1320511212=:70648"
Subject: Re: [Bitcoin-development] Lock protocol version numbers
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>

---71337780-990759556-1320511212=:70648
Content-Type: text/plain; charset=us-ascii


On Saturday, November 05, 2011 12:17:58 PM Christian Decker wrote:
>> Sorry for shooting this approach down, but I'm against it. User-agent
>> strings are an extremely bad idea as it would lead developers to start
>> making communication choices depending on the client type.
> This can be necessary in some cases. What happens when some popular client is 
> found with a subtle bug, and cannot otherwise be differentiated from other 
> similar-functionality clients? I have found User-Agent very valuable when 
> dealing with the wide variety of miner bugs when I have enabled new 
> functionality/behaviour on Eligius.

I can agree with this point though. If clients break the network protocol/do not comply properly with it, they should be disconnected and shunned. Hard love. We don't want any ambiguity in the protocol.

Fail hard and fast.

However my feeling about the user-agent string is that it is a vanity item, but here we'd be enforcing a format that everybody can understand and read. Lets say with libbitcoin- I'm sure that users of libbitcoin would like to have their client name in the string somehow. This was we can quickly understand which code-bases are being used and all the variants that exist build on those code-bases.

Together with system information (how many Linux users are there?) and various system settings (how many 32bit users are there), and so on.

---71337780-990759556-1320511212=:70648
Content-Type: text/html; charset=us-ascii

<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><br><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;">
On Saturday, November 05, 2011 12:17:58 PM Christian Decker wrote:<br>&gt;&gt; Sorry for shooting this approach down, but I'm against it. User-agent<br>&gt;&gt; strings are an extremely bad idea as it would lead developers to start<br>&gt;&gt; making communication choices depending on the client type.<br>&gt; This can be necessary in some cases. What happens when some popular client is <br>&gt; found with a subtle bug, and cannot otherwise be differentiated from other <br>&gt; similar-functionality clients? I have found User-Agent very valuable when <br>&gt; dealing with the wide variety of miner bugs when I have enabled new <br>&gt; functionality/behaviour on Eligius.<br><br>I can agree with this point though. If clients break the network protocol/do not comply properly with it, they should be disconnected and shunned. Hard love. We don't want any ambiguity in the protocol.<br><br>Fail hard and fast.<br><br>However my feeling about the user-agent string
 is that it is a vanity item, but here we'd be enforcing a format that everybody can understand and read. Lets say with libbitcoin- I'm sure that users of libbitcoin would like to have their client name in the string somehow. This was we can quickly understand which code-bases are being used and all the variants that exist build on those code-bases.<br><br>Together with system information (how many Linux users are there?) and various system settings (how many 32bit users are there), and so on.<br></div></div></div></body></html>
---71337780-990759556-1320511212=:70648--