W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2022

Re: Draft for Resumable Uploads

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 12 Apr 2022 07:48:36 +0200
Message-ID: <5ae62ba2-39d0-84e1-3733-992bd3aa4d64@gmx.de>
To: ietf-http-wg@w3.org
Am 12.04.2022 um 01:50 schrieb Eric J Bowman:
> All snark aside (sorry about that, Austin, all)...
>
>  >
>  >-----------------
> PATCH (RFC 5789) specifically permits resource creation
> <https://httpwg.org/specs/rfc5789.html#patch>:
>
>
>         If the Request-URI does not point to an existing resource, the
>         server MAY create a new resource, depending on the patch
>         document type (whether it can logically modify a null resource)
>         and permissions, etc.
>
>
>     So as long as the PATCH media type can describe creating a resource
>     (which this does), PATCH can create resources.
>      >-----------------
>      >
>
>
> The reason I think this is bad protocol design to the point it makes my
> brain explode, is it introduces the notion that method semantics vary by
> media type. The interface is now resource-specific, rather than generic.
> Transparency is lost because the message is not self-descriptive, e.g.
> intermediaries would require a lookup table of media types in order to
> determine method semantics.

Not really. The semantics of PATCH is "apply the payload as patch to
whatever the current representation of the resource is". That includes
resources with no current representation.

Best regards, Julian
Received on Tuesday, 12 April 2022 05:48:52 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 12 April 2022 05:48:53 UTC