Branko Čibej schreef:
> David Glasser wrote:
>> On Jan 22, 2008 9:07 AM, Branko Čibej <brane_at_xbc.nu> wrote:
>>
>>> Bah. --pre-1.4.x-compatible is for old clients accessing via file://.
>>> svndiff0 over the wire is for old clients, period. I think burning that
>>> bit all the way through our APIs is more hassle than upgrading clients.
>>>
>>
>> I'll buy that for the FS; although it's also for "old repositories who
>> haven't done a dump and load, the only officially supported way of
>> upgrading repository format", I suspect that 1.5 will require an
>> "svnadmin upgrade" command anyway.
>>
>
> IMHO the inconvenience of forcing an upgrade of clients that access the
> repository locally is mitigated by the fact that they /do/ access the
> repository locally, in other words, it's quite likely that you'll have
> complete control over the client version when you upgrade the server and
> the repository.
>
>> Do we have actual numbers on client versions anywhere? It wasn't long
>> ago that it was uncommon to find 1.4 in stable versions of various
>> distributions.
>>
>
> I don't think that's so important. Remember that we never send actual
> data from the repo to the client; it's always munged and deltas
> recomputed in some way. So this over-the-net slowdown would only affect
> pre-1.4 clients talking to a 1.5 server during initial checkout, when we
> can't send deltas.
And, I suspect, new file checkins from the new clients to the old
servers. But yes, the point would be that this happens relatively
rarely, mostly during inital checkout, and export I think.
I am not in favour of updating the API. It is a big hassle and like you
said before, it is "only" a performance issue, not a compatibility
issue. But then, who am I to say? :)
Regards,
Niels
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-24 14:44:58 CET