On Wed, Sep 26, 2012 at 9:44 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Wed, Sep 26, 2012 at 9:40 AM, Philip Martin <philip.martin_at_wandisco.com
> > wrote:
>
>> Mark Phippard <markphip_at_gmail.com> writes:
>>
>> > What happens with Serf? From what I know, I would assume that Serf has
>> to
>> > do a GET of the entire file. Is this true or does it somehow only
>> request
>> > a delta?
>>
>> Serf sends the delta base to the server (what does TEMPORARILY mean
>> here?):
>>
>> /** This header is *TEMPORARILY* used to transmit the delta base to the
>> * server. It contains a version resource URL for what is on the client.
>> */
>> #define SVN_DAV_DELTA_BASE_HEADER "X-SVN-VR-Base"
>>
>> so a GET looks like:
>>
>> GET /obj/repo/!svn/rvr/2/f HTTP/1.1
>> Host: localhost:8888
>> User-Agent: SVN/1.8.0-dev serf/1.1.1
>> DAV: http://subversion.tigris.org/xmlns/dav/svn/depth
>> DAV: http://subversion.tigris.org/xmlns/dav/svn/mergeinfo
>> DAV: http://subversion.tigris.org/xmlns/dav/svn/log-revprops
>> X-SVN-VR-Base<http://subversion.tigris.org/xmlns/dav/svn/log-revpropsX-SVN-VR-Base>:
>> /obj/repo/!svn/rvr/1/f
>> Accept-Encoding: svndiff1;q=0.9,svndiff;q=0.8
>>
>>
> OK, thanks. I see that is documented here:
>
>
> http://svn.apache.org/repos/asf/subversion/trunk/notes/http-and-webdav/webdav-protocol
>
>
> I assumed it must send deltas somehow or we would be noticing performance
> issues.
>
>
I have always been skeptical of the ability to put a cache in front of the
SVN server. Wouldn't something like this keep a cache from working
properly? How would a cache know about that header we added and that the
content we returned to the client cannot be cached? I presume we set
something in the response that an intelligent cache would look at and know
that it cannot cache the response. But that effectively means the cache
would only provide some value on checkout?
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2012-09-26 15:57:57 CEST