> On 26 Jan 2015, at 12:04, Francesco Mari <[email protected]> wrote: > > The document I posted uses JSON only as a simple way to describe > generic data structures. There is a big disclaimer at the beginning of > "operations.md". The operations are supposed to be described in an > abstract way, without any procol-dependent technology. Please, let's > evaluate "operations.md" without thinking so much about JSON, JSOP or > other serialization strategies. > > That said, since the topic was brought up, I have to admit that I'm > not a big fan of JSOP. I don't see any benefit in that format, since > it doesn't really add anything that couldn't be done with plain JSON, > if I understand correctly.
well that is the idea .. as its based on JSON :) it essentially extends JSON to specifically make it possible to express PATCH type requests in the context of a content repository. stuff like re-ordering etc. in that sense its also useful to handle the issue you talk about: dealing with multiple changes that you might have inside a remote session without needing a session, since you can do it all in a single request. regards, Lukas Kahwe Smith [email protected]
signature.asc
Description: Message signed with OpenPGP using GPGMail
