Re: DAV update problem (was: more handy post-M3 tips)

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?

For small updates, that second connection is relatively expensive.

Joe also had excellent points about the timeouts and the authentication,
both good reasons for why I didn't feel two sessions was a good idea.

> > Buffering in memory could be impossible for a large update.
>
> Absolutely. It would also violate our "streaminess" promise. (A promise
> we aren't keeping right now, though.)
>
> >Setting and abandonment threshold isn't all that attractive either...
>
> "Update abourted because there are too many changes in the repository."
> Brrr.

Right and right.

I believe the proper approach is to buffer X amount of data, then fall off
to temporary file. Replay those instructions to fetch the information.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org