RE: Resolution of open issues: JW4/DB4/DB5 (insufficient storage status code)

OK with me.

Alan Babich

-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: Friday, February 15, 2002 8:30 AM
To: dasl
Subject: RE: Resolution of open issues: JW4/DB4/DB5 (insufficient
storage status code)


Hi,

I didn't get any feedback at all. Can I take this as "ok, go forward with
this change"?

> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Julian Reschke
> Sent: Sunday, February 03, 2002 5:56 PM
> To: dasl
> Subject: Resolution of open issues: JW4/DB4/DB5 (insufficient storage
> status code)
>
>
> Currently, SEARCH is defined to return a status code of 507 (Insufficient
> Storage) when the result set was truncated [1]. The following issues were
> raised:
>
> - Don't use 507 for Insufficient Storage. Use a new code, perhaps 208
> (Partial Results).
> - When results are truncated, server replies with a 507 and also
> returns an
> XML element.
> - 507 is currently in conflict with other specs. Need to avoid collisions.
>
> I think an easy way to resolve this would be to consider to use 207
> (Multi-Status), and then to define how the client would detect a truncated
> result set: this could take the same format as in sectiom 2.5.1
> (the SEARCH
> arbiter resource would be reported with a 507 status code *inside* the
> multistatus response).
>
> Feedback appreciated,
>
> Julian
>
>
>
> [1]
> <http://www.greenbytes.de/tech/webdav/draft-reschke-webdav-search-
> latest.htm
> l#rfc.issue.JW4/DB4/DB5>
>
>
>

Received on Sunday, 17 February 2002 17:28:12 UTC