Re: [apps-discuss] JSON patch: "test" operation

Julian:

Is the thinking that _clients_ should tell servers to test an
insert/update?  IOW, clients would want to see test results?  A "dry run"
scenario?

Also, was there any talk about how servers would handle failed tests (HTTP
Response code, etc.)? If one or more tests fail, would the server have the
option of making the changes and then returning a list of success/fail
information?

mca
http://amundsen.com/blog/
http://twitter.com@mamund
http://mamund.com/foaf.rdf#me

On Wed, Nov 30, 2011 at 12:09, Paul C. Bryan <paul.bryan@forgerock.com>wrote:

> **
> Yes, assert/equals/test has been mentioned in the past. As you point out,
> HTTP preconditions to handle this to some extent. I've avoided adding it
> thus far mostly because I haven't had a single concrete use case outside of
> HTTP. Given at least the pattern of multiple requests wanting to test a
> value for equality, I think I have enough data to add it to the next
> revision of the spec. Consider it added.
>
> Paul
>
> On Wed, 2011-11-30 at 16:22 +0100, Julian Reschke wrote:
>
> Hi,
>
> this came up during discussions of patch formats on the Apache
> jackrabbit-dev mailing list:
>
> Would it make sense to add a "test" operation that allows checking the
> state of the JSON object to be modified?
>
> It would be consistent with other diff formats that use context
> information in order to check whether the patch "cleanly applies".
>
> An example would be:
>
>     [
>           { "test": "/vsn", "value" : 17 },
>           { "replace": "/vsn", "value" : 18 },
>           { "replace": "/balance", "value": 1234 }
>     ]
>
> And yes, concurrency control can also be achieved using conditional HTTP
> methods, but that doesn't mean that they don't make sense in the patch
> format as well.
>
> Best regards, Julian
> _______________________________________________
> apps-discuss mailing listapps-discuss@ietf.orghttps://www.ietf.org/mailman/listinfo/apps-discuss
>
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>