News for hackers. Stuff that matters.
Re:PATCH Method for HTTP by scott_w on Wednesday July 04, 2012 @07:10AM (#4198854)
It's a shame that Patch isn't idempotent.

My preference for updating data across the web is to send only the information that is different, and the service ensures everything else remains the same. Put doesn't quite cut it in this case (technically, it's supposed to completely replace a resource).

Are there any advantages for declaring Patch to be not idempotent? I'm assuming it allows appending to a single resource?

Re:PATCH Method for HTTP by _mhp_ on Wednesday July 04, 2012 @08:38AM (#4199125)
Section 2 contains:

  A PATCH request can be issued in such a way as to be
  idempotent, which also helps prevent bad outcomes [...]
  Clients using this kind of patch application SHOULD use
  a conditional request [...]  For example, the client
  can use a strong ETag [RFC2616] in an If-Match header on
  the PATCH request.
So you can, but aren't obliged to.
Re:PATCH Method for HTTP by quesera on Wednesday July 04, 2012 @07:45AM (#4198961)
HTTP PATCH can only be idempotent if the underlying patch mechanism is idempotent, right?

At the protocol level, there are no guarantees. At the application level, you can fake it (in the non-mathematical sense) by checking sentinels/guids or testing for applicability. This provides safety, but requires code.

But that's not really idempotence. I don't see any way that the IETF could specify a generic idempotent patch mechanism, or declare an arbitrary mechanism to be idempotent.

EDIT: it looks like you want idempotence a la SQL UPDATE. That seems eminently doable in the application layer. Specifying it in an RFC would be inadequately generic for a whole new HTTP verb, I think.

Re:PATCH Method for HTTP by rmccue on Wednesday July 04, 2012 @08:03AM (#4199022)
By definition, GET, HEAD, PUT and DELETE are idempotent: http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html

I personally agree with the parent. PATCH should be idempotent; overwriting values with new values is idempotent and that should be written into the spec rather than avoiding it in favour of things like writing logs (which IMHO should be a POST).

Re:PATCH Method for HTTP by quesera on Wednesday July 04, 2012 @08:19AM (#4199075)
Yes, but GET, HEAD, PUT, and DELETE do very different things.

You can write an idempotent PATCH mechanism. If that's what you want, you can do it. You control the server, so you can restrict the accepted patch formats to idempotent ones.

Adding an HTTP verb doesn't make patching magically happen. Someone has to write the logic, either you or your framework authors. Obviously there will be different mechanisms and some will be effectively idempotent. Again, not in the mathematical or functional programming sense, but in the colloquial DBA sense, at least.

Limiting HTTP PATCH at the protocol level would be a huge mistake, I think.

None of this should be construed to mean that I see a clear need for a new HTTP verb, though.

Re:PATCH Method for HTTP by Xylakant on Wednesday July 04, 2012 @08:45AM (#4199156)
Note of care: SQL Updates are not idempotent. "UPDATE table SET a = a + 1".
Re:PATCH Method for HTTP by nfriedly on Thursday July 05, 2012 @06:10PM (#4205259)
I love that for rearranging items in lists with user-defined orders. It lets you update the entire set with two commands - one to give the moved item its new position, and one to increase the position of every item after it.
Re:PATCH Method for HTTP by bruth on Wednesday July 04, 2012 @09:08AM (#4199253)
Conditional requests are the way to go to be more transparent to clients, but the server implementation can _test_ values prior to patching the resource. For example, the JSON Patch spec has a "test" operation: http://tools.ietf.org/html/draft-ietf-appsawg-json-patch-02#... so you could accept the same patch, but simply test if the resource is up-to-date before patching it.
Re:PATCH Method for HTTP by ibotty on Wednesday July 04, 2012 @07:22AM (#4198890)
yes. to quote the rfc:

   There are also cases where patch formats do not need to operate from
   a known base-point (e.g., appending text lines to log files, or non-
   colliding rows to database tables) [...]
Re:PATCH Method for HTTP by scott_w on Wednesday July 04, 2012 @07:26AM (#4198903)
Yes, I saw that.

Personally, I think Post does a good enough job for that. I know it's technically supposed to create a sub-resource, but it seems to work for appending to the same resource just as well.

I'm a little uncertain of the case for using Patch to append rows to a database. Surely that's a case where Post does a better job?

Re:PATCH Method for HTTP by rfugger on Wednesday July 04, 2012 @08:59AM (#4199213)
POST would make more sense if each row is its own resource. PATCH would make more sense if the entire table is its own resource, without addressable sub-resources (rows).
Re:PATCH Method for HTTP by scott_w on Wednesday July 04, 2012 @09:19AM (#4199290)
As far as the spec is concerned, yes I agree.

On a more personal level, I'm of the opinion that Post can append to an existing resource, without adding a new resource.

Allowing for this practicality in the spec would allow Patch to be only idempotent.

Re:PATCH Method for HTTP by ibotty on Wednesday July 04, 2012 @12:30PM (#4199958)
that would be nice, indeed, but seems impossible now.
Re:PATCH Method for HTTP by zacharyvoase on Wednesday July 04, 2012 @02:25PM (#4200348)
Coincidentally, I recently read this article, entitled “You Cannot Correctly Represent Change Without Immutability”: http://tapestryjava.blogspot.se/2012/07/you-cannot-correctly...

The point is, the ‘patch’ itself is a transformation defined by a 2-tuple of the old value and the delta (whereas a ‘put’ would be defined as the 2-tuple of the old value and the new value). Because the old value is referenced by the request URI (which is mutable), simply specifying the delta itself is not idempotent. Of course, following the RFC's advice and adding the ETag means you're specifying both the delta and the old value, which makes the operation idempotent.

Re:PATCH Method for HTTP by m_eiman on Wednesday July 04, 2012 @08:07AM (#4199043)
Wouldn't combining it with an If-Match header make it idempotent, assuming the server actually performs the check before applying the patch?
Re:PATCH Method for HTTP by zedr on Wednesday July 04, 2012 @09:06AM (#4199243)
Concurrent clients PUTting and PATCHing of a single resource. Successive (not sequential) PATCHes are not guaranteed to produce the same outcome.