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

Re: Status of ra_serf

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2006-02-17 16:54:46 CET

Justin Erenkrantz wrote:
> On 2/17/06, C. Michael Pilato <cmpilato@collab.net> wrote:
>
>>I'm not sure why this is a problem /you/ have, though. The spooling
>>decision/implementation code is completely within libsvn_ra_dav.
>
>
> I must be seeing something else then. What I see is httpd/mod_dav_svn
> open 'report.tmp' and write to it as it scans through the fsfs
> repository. Does that ring any bells? -- justin

That's the REPORT *request*, which is always spooled to disk (and long
pre-dates my bugfix). IIRC, we spool the report to disk because Neon
has pull interface for request bodies -- either pull the request from a
file, or pull it from a memory buffer. We'd prefer to push the request
at Neon so we can fire it off streamily.

But what I was talking about was the spooling of the REPORT *response*.

-- 
C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on Fri Feb 17 17:08:29 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.