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

Re: more handy post-M3 tips

From: Joe Orton <joe_at_manyfish.co.uk>
Date: 2001-09-04 23:00:16 CEST

On Tue, Sep 04, 2001 at 06:42:32PM +0200, Branko �ibej wrote:
> Greg Stein wrote:
> >Hoo boy... this is going to be an ugly one to fix. The cheap way is to open
> >a second session, but I don't like that one at all.
> >
> Um. What's wrong with opening a second session? Use one for reading the
> REPORT, and another for all the GETs, PROPFINDs and whatnot. That means
> you always use two, not 1+N sessions, right?

Yes, fixed at two sessions. I think the worst thing is that the first
session will be blocked while the second session does its thing. Imagine
session 1 does the REPORT, then half way through reading the response,
we have to GET a 200Mb document. By the time the client has finished
that, the server may have timed out the REPORT request and aborted that

Maybe that would be okay, if the REPORT is then restarted correctly, and
doesn't have to do the 200Mb GET again. I guess that would work.

Each session would have to renegotiate authentication, which might be an

Anyway, I might try and implement this, because I can't update my
working copy until this bug is fixed! :) See how it goes...


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:40 2006

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.