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

Re: Sorted output from Subversion commands

From: Kevin Puetz <puetzk_at_puetzk.org>
Date: 2005-02-23 05:49:28 CET

kfogel@collab.net wrote:

> Branko Čibej <brane@xbc.nu> writes:
>> Now the question: Can we, according to our versioning rules, demand
>> that a client never uses two different versions of the same function
>> at the same time? In other words, if we add svn_wc_entries_read2, can
>> we modify svn_wc_entries_read to return an error if the entries cache
>> contains the wrong type of structure?
> Suppose you write library X, against the Subversion 1.0 API. Then I
> write library Y, against the 1.2 API. Now application A comes along
> and uses *both* X and Y, passing data structures back and forth
> between them.
> This would mean that adm_access batons would not be exchangeable in
> this way, even though they are the exact same type in both libraries.
> I think that would be very difficult to document, and difficult for
> people to code around.
> So, I am forced to conclude that we can't make such a demand.

If it's possible to return an error, I presume it's possible to in some way
detect when the wrong structure is stored. Wouldn't it then be possible to
just invalidate the cache in such a case (presuming it's actually a cache)
and read from whatever the authoritative source is? Admittedly, that
wouldn't be very fast, but the even when mixing library versions like this
it would still work then...

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 23 05:51:53 2005

This is an archived mail posted to the Subversion Dev mailing list.

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