Rev 2441: Update protocol versioning docs to explain how unknown request versions should be handled. in http://bazaar.launchpad.net/~bzr/bzr/hpss-protocol2

[Andrew Bennetts]

At http://bazaar.launchpad.net/~bzr/bzr/hpss-protocol2

------------------------------------------------------------
revno: 2441
revision-id: andrew.bennetts at canonical.com-20070426043244-l1gtjevl8f98jbnk
parent: andrew.bennetts at canonical.com-20070425054002-08sj7lxphtpb6ewm
committer: Andrew Bennetts <andrew.bennetts at canonical.com>
branch nick: hpss-protocol2
timestamp: Thu 2007-04-26 14:32:44 +1000
message:
  Update protocol versioning docs to explain how unknown request versions should be handled.
modified:
  bzrlib/smart/__init__.py       __init__.py-20061101100249-8jwwl0d3jr080zim-1
=== modified file 'bzrlib/smart/__init__.py'
--- a/bzrlib/smart/__init__.py	2007-04-25 05:40:02 +0000
+++ b/bzrlib/smart/__init__.py	2007-04-26 04:32:44 +0000
@@ -84,6 +84,11 @@
 This is that clients and servers can read bytes up to the first newline byte to
 determine what version a message is.
 
+For compatibility will all versions (past and future) of bzr clients, servers
+that receive a request in an unknown protocol version should respond with a
+single-line error terminated with 0x0a (NEWLINE), rather than structured
+response prefixed with a version string.
+
 Request/Response processing
 ---------------------------