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

RE: Subversion Issue 773

From: Julian Reschke <julian.reschke_at_gmx.de>
Date: 2003-01-03 01:12:43 CET

> From: Greg Stein [mailto:gstein@lyra.org]
> Sent: Thursday, January 02, 2003 11:23 PM
> To: Brandon Ehle
> Cc: dev@subversion.tigris.org
> Subject: Re: Subversion Issue 773
> ...
> The PROPFIND handling was written back in 1998 before Apache 2.0
> and bucket
> brigades ever existed. It was also at a point in time where a lot of
> properties weren't around, and I simply never heard of a problem with the
> memory consumption which would necessitate a streaming option. Also, the
> "buffer it in memory" means that you can return a meaningful error message
> if something goes wrong. If you've streamed out the properties
> for half the
> resources and *then* something goes wrong, it is rather difficult
> to notify
> the client of that problem (most clients only look at the HTTP status line
> rather than the status records in the propstat tags).
> ...

That would be a *really* buggy client, wouldn't it?

All clients de-facto must be able to understand DAV:propstat elements with
status 200 and 404, so I'd be surprised if anybody would accept a property
with a non-200 DAV:propstat as a valid property value.

Or am I missing something?


<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 3 01:13:53 2003

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.