Re: GSOC idea: json api for plone

Jens W. Klein wrote:
> On 2014-02-25 08:26, Asko Soukka wrote:
>> Sean Upton wrote:
>>>> IMO it would be a good start to make all plone.api calls available as
>>>> json-rpc. Also (with some level of abstraction on serialization/
>>>> deserialization) then it is easy to get at the same time an xmlrpc api.
>>> +1 to abstracting serialization model.
>> How should this relate to plone.rfc822
>> (https://pypi.python.org/pypi/plone.rfc822), which AFAIK is the current
>> standard serialization/deserialization model?
>
> Plone already had this rfc822 style in back in old archetypes
> marshallers. I never liked it. It was clumsy to handle
>
> I like the base idea behind: Add additional information to the schema
> where needed an use it to serialize it. The same is possible with
> deserialization.

So, plone.jsonld (or whatever) could follow the design of plone.rfc822 
and re-use its primary field marker used in Dexterity schemas? I wonder, 
if it would speed up the development, if it would be allowed to re-use 
the existing plone.rfc822-marshal-adapters. Of couse, it dependency on 
plone.rfc822 could be a problem later.

> I dont think rfc822 headers are what we want to have. In json there are
> better suited structures around. It would end up in a text-block
> packaged in json, the client has to parse the text block again. Too much.

Agreed. You cannot really serialize e.g. datagridfield or other complex 
schemas into sane rfc822 headers.

-Asko

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk