Considering moving all Launchpad branches to 2a - based formats

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/14/2011 3:10 PM, Aaron Bentley wrote:
> On 11-09-14 04:34 AM, Martin Pool wrote:
>> .... I guess after that we need some announcement that it will 
>> happen, and possibly to contact people who are using old
>> clients.
> 
> Certainly if we decide to execute this, we'll announce it.  I
> hadn't thought of contacting users of old clients, though.
> 
>> I think that you may be able to look at the xmlrpc access logs
>> for user-agents to see how many old clients are out there.
> 
> I actually thought bzr didn't send a version string.  Happy to be 
> wrong about that.
> 
> Aaron

Since we implemented "Protocol version 3" of the bzr:// protocol, it
sends a header section. As near as I can tell, nothing is actually
done with those headers.


It looks like both the client and the server are using the default of:
        self._headers = {'Software version': bzrlib.__version__}

However:
  MESSAGE_VERSION_THREE = 'bzr message 3 (bzr 1.6)\n'

That also means that the older clients for bzr 1.3, etc, won't be
setting the version headers. Then again, for old versions like that,
we can just tell that they are using:
  REQUEST_VERSION_TWO = 'bzr request 2\n'

As their first request.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5wrLcACgkQJdeBCYSNAAN6twCgu+gtbX/7caDFooaE6LlEHVtn
QJMAn3ypllrWLT03OHlIYNy9xbN3XyRc
=285h
-----END PGP SIGNATURE-----