Next message: Ron Jacobs: "RE: comments on deltav-08.2"
Message-ID: <CC2AF3B5727BD411907F00A0CC63594C0F0962@exchange.gforcesystems.com>
From: Ron Jacobs <rjacobs@gforce.com>
To: ietf-dav-versioning@w3.org
Date: Fri, 22 Sep 2000 16:09:43 -0700
Subject: DAV:version-set
I think this topic has been discussed before, but for me the issue is still
alive as of the 08.2 spec.
Is the DAV:version-set property (section 14.2.1) required to be implemented
by a server?
I am designing a versioning server that routinely may have thousands (or
perhaps hundreds of thousands) of versions of a resource. (Yep, you read
that correctly :)
Do I have to be able to return that many version URLs? I would be happier
relying upon predecessor and successor properties as well as the
DAV:version-tree-report.
On a very related topic, hasn't there been discussion regarding whether (and
how) a server may limit the size of its response bodies, especially for
reports? I can't find any mention of this in the current draft. How has the
issue been resolved?
Wouldn't the Range request header and Content-Range entity header be useful
for breaking up large responses into multiple request/response pairs? How
does a REPORT with a potentially huge response differ from a GET of a
potentially huge document? Is there anything that would preclude such an
implementation?
Thanks, Ron