References: <1320268981.72296.YahooMailNeo@web121003.mail.ne1.yahoo.com>
	<CANEZrP1OpuE1AHj1ARsGSkpkAwUQAr1_JaU=i4pjyERO6__+1A@mail.gmail.com>
	<CALxbBHXRWjdpttLeGcPrdd4uwVs=kg4QL5Q4fmBghfxTA60Kag@mail.gmail.com>
	<1320507570.40074.YahooMailNeo@web121017.mail.ne1.yahoo.com>
Message-ID: <1320507589.87534.YahooMailNeo@web121019.mail.ne1.yahoo.com>
Date: Sat, 5 Nov 2011 08:39:49 -0700 (PDT)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <1320507570.40074.YahooMailNeo@web121017.mail.ne1.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="911381700-1624615356-1320507589=:87534"
Subject: Re: [Bitcoin-development] Lock protocol version numbers
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>

--911381700-1624615356-1320507589=:87534
Content-Type: text/plain; charset=us-ascii

From talking with Patrick Strateman (phantomcircuit), he suggested this idea (which I will elaborate more on in the BIP):


User-agent strings are a good starting point, however they aren't easy for parsing so we'll make a small modification to them.

We need a hierarchy from protocol, variant, gui, flavour, build

/Satoshi:314700/bitcoin-qt:0.4/

How does that sound? In BitcoinJ's case:

/BitcoinJ:0.2/AndroidBuild:0.8/

Thoughts:

- Do we need a freely defined comments field?

/BitcoinJ:0.2[iPad; U; CPU OS 3_2_1]/AndroidBuild:0.8/
/Satoshi:314700/bitcoin-qt:0.4[Ubuntu Oneiric]/


________________________________
From: Christian Decker <decker.christian@gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Amir Taaki <zgenjix@yahoo.com>; "bitcoin-development@lists.sourceforge.net" <bitcoin-development@lists.sourceforge.net>
Sent: Saturday, November 5, 2011 2:45 PM
Subject: Re: [Bitcoin-development] Lock protocol version numbers


On BitDroid I stopped updating the protocol version at 31700 and set the string to be both Version and Client, just like BitcoinJ :-)


On Sat, Nov 5, 2011 at 3:32 PM, Mike Hearn <mike@plan99.net> wrote:

BitCoinJ already sets the subver field to its name and version.
>
>
>------------------------------------------------------------------------------
>RSA(R) Conference 2012
>Save $700 by Nov 18
>Register now
>http://p.sf.net/sfu/rsa-sfdev2dev1
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--911381700-1624615356-1320507589=:87534
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"><span>From talking with Patrick Strateman (phantomcircuit), he suggested this idea (which I will elaborate more on in the BIP):</span><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;"><div id="yiv1943267884"><div><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt;"><div><br><span></span></div><div><span>User-agent strings are a good starting point, however they aren't easy for parsing so we'll make a small modification to them.</span></div><div><br><span></span></div><div><span>We need a hierarchy from protocol, variant, gui, flavour,
 build</span></div><div><span><br></span></div><div><span>/Satoshi:314700/bitcoin-qt:0.4/</span></div><div><br><span></span></div><div><span>How does that sound? In BitcoinJ's case:</span></div><div><br><span></span></div><div><span>/BitcoinJ:0.2/AndroidBuild:0.8/</span></div><div><br><span></span></div><div><span>Thoughts:</span></div><div><br><span></span></div><div><span>- Do we need a freely defined comments
 field?</span></div><div><br><span></span></div><div><span>/BitcoinJ:0.2[iPad; U; CPU OS 3_2_1]/AndroidBuild:0.8/</span></div><div><span>/Satoshi:314700/bitcoin-qt:0.4[Ubuntu Oneiric]/<br></span></div><div><br></div><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;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight:bold;">From:</span></b> Christian Decker &lt;decker.christian@gmail.com&gt;<br><b><span style="font-weight:bold;">To:</span></b> Mike Hearn &lt;mike@plan99.net&gt;<br><b><span style="font-weight:bold;">Cc:</span></b> Amir Taaki &lt;zgenjix@yahoo.com&gt;; "bitcoin-development@lists.sourceforge.net" &lt;bitcoin-development@lists.sourceforge.net&gt;<br><b><span style="font-weight:bold;">Sent:</span></b> Saturday, November 5, 2011 2:45 PM<br><b><span style="font-weight:bold;">Subject:</span></b> Re:
 [Bitcoin-development] Lock protocol version numbers<br></font><br>
<div id="yiv1943267884">On BitDroid I stopped updating the protocol version at 31700 and set the string to be both Version and Client, just like BitcoinJ :-)<br><br><div class="yiv1943267884gmail_quote">On Sat, Nov 5, 2011 at 3:32 PM, Mike Hearn <span dir="ltr">&lt;<a rel="nofollow" ymailto="mailto:mike@plan99.net" target="_blank" href="mailto:mike@plan99.net">mike@plan99.net</a>&gt;</span> wrote:<br>

<blockquote class="yiv1943267884gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">BitCoinJ already sets the subver field to its name and version.<br><br>
<br>------------------------------------------------------------------------------<br>
RSA(R) Conference 2012<br>
Save $700 by Nov 18<br>
Register now<br>
http://p.sf.net/sfu/rsa-sfdev2dev1<br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a rel="nofollow" ymailto="mailto:Bitcoin-development@lists.sourceforge.net" target="_blank" href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
<a rel="nofollow" target="_blank" href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
<br></blockquote></div><br>
</div><br><br></div></div></div></div></div><meta http-equiv="x-dns-prefetch-control" content="on"><br><br></div></div></div></body></html>
--911381700-1624615356-1320507589=:87534--