W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2003

RE: Tamino WebDAV Server's PUT implementation

From: Julian Reschke <julian.reschke@greenbytes.de>
Date: Thu, 13 Mar 2003 17:49:51 +0100
To: "Jeffrey Winter" <jeffreywinter@crd.com>, <ietf-dav-versioning@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCKEANGMAA.julian.reschke@greenbytes.de>
Hi.

First of all, this isn't really about WebDAV or DeltaV -- it's a generic
HTTP question.

I'd say that yes, a server may use "lossy" ways to persist entities. After
all, all HTTP is giving you are methods that get/set certain
*representations* of resources.

Now of course this will fail if your client assumes that it can round-trip
octet-by-octet. In which case I'd recommend just to use a different server
(or backend within that server). It's a backend optimized for a specific use
case (storing XML infosets). If this doesn't fit into your requirements, use
something else.

Julian
--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

  -----Original Message-----
  From: ietf-dav-versioning-request@w3.org
[mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Jeffrey Winter
  Sent: Thursday, March 13, 2003 5:21 PM
  To: ietf-dav-versioning@w3.org
  Subject: Tamino WebDAV Server's PUT implementation


  I have a question regarding the Tamino WebDAV Server's
  implementation of the PUT method.

  It appears that when PUTing an XML document, Tamino stores it
  preserving the XML infoset but not the actual byte-for-byte
  layout of the document, so for example, PUTing:

    <hello></hello>

  will be retrieved using GET as:

    <hello/>

  I've seen some discussion stating that the server must
  maintain octet-for-octet fidelity of the entity enclosed
  in the PUT request.

  Is Tamino's implementation wrong or is my description of
  PUT too strict?

  Thanks.
Received on Thursday, 13 March 2003 11:50:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:44 GMT