Loading ...
Sorry, an error occurred while loading the content.

9407Re: Content-Range (was: The Ambiguous Semantics of PUT: Complete or Incomplete Representations)

Expand Messages
  • A. Pagaltzis
    Jul 10, 2007
    • 0 Attachment
      * Stian Soiland <ssoiland@...> [2007-07-04 15:05]:
      > What about PUTing with the Content-Type: multipart/byteranges
      > [1]? If the server don't understand multipart/byteranges, it
      > will say 406 Not Acceptable.

      If the server accepts any MIME type for the resource at that URI,
      then it will try to store the patch as the content of the
      resource. If arbitrary media types are not acceptable, the PUT
      will probably be rejected. That’s what PUT means.

      > It has already been agreed that since all representations
      > are/can be partial on GET, so would representations that are
      > uploaded with PUT often be partial.

      Sure, but it’s a red herring here. The fact that a client can’t
      fill in all aspects of the resource with a single representation
      doesn’t mean that it *intends* the missing aspects to be filled
      in from the previous state of the resource; it merely gives the
      server licence to fill them in appropriately, probably by setting
      them to some default state, although deriving from some previous
      state of the resource is also legal.

      The difference between PUT and PATCH is that with the latter, the
      client is explicitly requesting that the previous state of the
      resource be taken into account, and that the entity body it sends
      is not a (possible) rendition of the resource, but a rendition of
      the differences between the previous state of the resource and
      the intended new state.

      Aristotle Pagaltzis // <http://plasmasturm.org/>
    • Show all 102 messages in this topic