What to do about HPSS protocol backwards compatibility for faster push?
Martin Pool
mbp at sourcefrog.net
Thu Oct 18 04:46:35 BST 2007
> 1) always try the large request, and then fallback.
> 2) always try the large request, and then fallback, but also warn the user
> that they should upgrade the server to get much better performance.
> 3) send a "do you support request X?" request first (possibly integrate this
> into the existing "hello" request).
> 4) add a configuration option to locations.conf so that users can turn off
> this feature for known-old servers.
> 5) add a configuration option to the client to enable it (and have the feature
> by off by default).
I think option 2 is fine for now. Configuration options to either
disable particular smartserver commands, or disable warnings about
them not working, might be generally useful but I don't think they're
a high priority.
I think this would be a good time to have a system for marking rpcs
with the version they were introduced, so that we can run new code
against a simulation of the old code.
In future we probably do want a way to have the server interrupt a
sending client with an error (and more information than just dropping
the connection), but that may be protocol-specific.
--
Martin
More information about the bazaar
mailing list