On Thu, Sep 20, 2012 at 4:35 AM, Andreas Krey <a.krey_at_gmx.de> wrote:
> On Thu, 20 Sep 2012 06:36:02 +0000, Nico Kadel-Garcia wrote:
>> here! By keeping the software an integrated codebase for clients and
>> servers, they're able to make protocol changes that you'll be forced
>> to keep up with in an entirely distinct codebase. How can you *test*
>> that robustly?
>
> That is just shifting the problem. Either you have an API that you can't
> just modify, or you consider the wire protocol your API, and either way
> you have to be backwards-compatible and need something to test on that
> level. (Besides in my opinion the wire protocol is only that complex
> because you don't replicate - moving whole commits is easier than doing
> all the commands remotely.)
It's worth pointing out that this problem isn't that big of a problem
for them. If they implement one version of our wireline protocol then
they are going to interoperate with us until we bump the major. Yes
they may be missing some features until they catch up, but they will
interoperate.
Received on 2012-09-20 18:51:07 CEST