[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: TortoiseSVN "Get lock" of multiple files fails via Java-SSL-tunnel since v1.9.0 (bug?)

From: Stefan Hett <stefan_at_egosoft.com>
Date: Fri, 6 May 2016 14:34:43 +0200

On 5/6/2016 2:28 PM, Stefan Küng wrote:
> On 06.05.2016 13:43, Stefan Hett wrote:
>>> TSVN of course uses the svn library APIs to do the locking.
>>> It passes all files to be locked to the API at once, and then the API
>>> would do the locking.
>> With regards to determine the impact from the Subversion project point
>> of view: Do you know whether that API was available in 1.8 already (aka:
>> passing multiple files to be locked) or whether that API was introduced
>> in 1.9 (and TSVN 1.8 used a different API)?
> The API was available in 1.8 as well (actually, the API hasn't changed
> since version 1.2). But the underlying protocol and how the svn lib
> handles the locks have changed. For example, when the API was introduced
> svn still used the neon lib for DAV requests, then came serf, and then
> neon was dropped. So a lot has changed under the hood.
K, that's changing the impact IMO.
Aka in this case it could be argued a regression in SVN 1.9 itself
(rather than only a bug) since the same API worked fine under the same
environment in 1.8 while it doesn't with 1.9... Let's see what the SVN
developers make out of that.

Stefan Hett, Developer/Administrator
EGOSOFT GmbH, Heidestrasse 4, 52146 Würselen, Germany
Tel: +49 2405 4239970, www.egosoft.com
Geschäftsführer: Bernd Lehahn, Handelsregister Aachen HRB 13473
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-05-06 14:34:54 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.