On 21 Jul 2014, at 2:17 pm, Y. Richard Yang <[email protected]> wrote:
> I am not sure I fully understand the context of it will "just-work." Just that the PATCH method is defined for generic mechanisms, not application-specific ones; if your payload is application-specific, you might as well use POST. > Here are some issues in our application-specific context, as Wendy pointed > out: > > 1. Ease-of-use: is there an easy-to-use library that just works: it produces > and applies JSON Patch based on existing JSON libraries? Do you have any > recommended pointers that we may check out? We have a test suite at: https://github.com/json-patch/json-patch-tests One of the community members keeps a list of implementations at: http://jsonpatch.com > 2. The issue of Set: JSON does not have a concept of a Set (e.g., a set of IP > prefixes). Hence, one typically uses an array to represent what actually is a > set. In setting where patching a set is simple, e.g., indicating the element > to be deleted. But indicating the op using the array is cumbersome: one has > to remember the array index. > > 3. Batching a set of operations: moving a subset of elements in a set. Yes, I can see how these would be difficult -- but they are possible. Note that we are starting to collect issues for a possible second version of json-patch: https://github.com/json-patch/json-patch2 ... and I've noted your feedback at: https://github.com/json-patch/json-patch2/issues/8 Please feel free to expand upon your requirements in that issue (and thanks for the feedback!). One approach you could take would be to use json-patch for now, and then use json-patch2 (or whatever it ends up being called) when it ships; that way, you avoid defining an application-specific patch format. Cheers, -- Mark Nottingham https://www.mnot.net/ _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
