Re: svn commit: r34914 - branches/http-protocol-v2/subversion/libsvn_ra_serf
On Fri, Jan 9, 2009 at 12:24 PM, Greg Stein <gstein_at_gmail.com> wrote:
> On Fri, Jan 9, 2009 at 09:33, Ben Collins-Sussman <sussman_at_red-bean.com> wrote:
>> Greg: you said that the old-fashioned code "can now cache the
>> youngest rev", but I don't see where that's happening. Is the cached
>> value somewhere *other* than in the global session_t?
> One more time, in small words :-)
> The old code DOES NOT cache the value.
> You are fetching the value.
> The new code has a place to hold a cached value.
> When running v2 mode, you cache the value in the proper place.
> When running v1 mode, you are NOW able to similarly cache the value.
> You can tweak the v1 code paths to NOW cache the value.
> Okee doke?
Nice. I guess there are two ways to interpret the phrase "X can now
do Y". You meant "X ought to be changed to do Y", while I heard "X
recently was changed to do Y". :-)
Received on 2009-01-09 22:23:15 CET
This is an archived mail posted to the Subversion Dev