Re: DAV:revision-resourcetype

From: jamsden@us.ibm.com
Date: Thu, Jan 27 2000

  • Next message: Geoffrey M. Clemm: "Re: DAV:revision-resourcetype"

    From: jamsden@us.ibm.com
    To: ietf-dav-versioning@w3.org
    Message-ID: <85256873.005932BF.00@d54mta03.raleigh.ibm.com>
    Date: Thu, 27 Jan 2000 09:55:57 -0500
    Subject: Re: DAV:revision-resourcetype
    
    
    
    <geoff>
    The main use of DAV:revision-resourcetype is to tell the server how to
    store the revisions of that versioned resource.  For a simple
    resourcetype (like text/xml), there might be several "storage types"
    (e.g. compressed, text-delta, binary-delta).
    </geoff>
    <jra>
    Why does the protocol ever have to deal with this? Can't the server store
    the bits any way it wants? The protocol should only be concerned with how
    the bits are communicated over the wire. The Accept* headers support this
    requirement. Servers have to be prepared to translate text into character
    sets requested by clients. To do this, they may choose to store the text in
    a canonical form efficient for their use and translate on request.
    </jra>