serialization

For those who are interested in the hypermedia part of Web Services, I wanted to call attention to a discussion posted in the WSCCI group, Proposing an alternative to application/vnd.drupal.ld+json.

The discussion is timeboxed to February 26th.

During the WSCCI Web Services Format Sprint last summer, JSON-LD was chosen as the front-runner for primary format. After that, we looked at what features of JSON-LD we would use and what use cases we wanted to support (summarized here).

I've been having a hard time drumming up architectural review on Handle entity references on import. I know it's pretty hard to see how the parts fit together, so I made a short video explaining the proposed approach.

The patch doesn't need code style review or manual testing yet, but instead needs architectural review to ensure we're building the right thing.

There's been lots of discussions on various approaches for serializing entities in the WSCCI group and with Drupal 8 feature freeze only a few months away, it's time to start coding. JSON-LD was chosen as a potential good candidate for serializing Drupal entities. One of the key features of JSON-LD is the ability to include a @context along with your data. This context describes the data present in the JSON document and is useful for consumers to understand how to best make use of the data.

In the story here, It was finally decided that we will be using JSON for passing the "data" from client to server. As discussed, we'll be storing details in a JS object array in client. Robert had said that it is preferable to convert JS to php on server.

1. What are the scenarios where serialized JS is prefered over php on server? Basically that answers why we should transfer the data in JS format instead of PHP?
2. Now, once we have the "data" to transfer, What are the possible ways to transfer this from client to server? Is form POST enough or is thr something else that can be used?