Content negotiation in Plone via dynamic layers about plone.restapi

[tisto]

Content negotiation is on our todo list. Though, we plan to focus on json exclusively first. I guess it should be possible to amend our IBeforeTraverseEvent hook to do pluggable content negotiation:

https://github.com/plone/plone.rest/blob/master/src/plone/rest/events.py

Ideas, requirements, code examples or any other contributions are more than welcome!

[metatoaster]

https://github.com/PMR2/pmr2.layer/tree/0.1/pmr2/layer

This is what I did some time ago but it does not address the complete syntax as documented in the HTTP/1.1 Header Field Definition (Section 14.1), but in general this shouldn't be a deal breaker as clients generally only want to deal with one specific format. For the most part, I did this mostly to provide canonical unique URL per resource (regardless of method of access) and versioning of the API (version 0 did not use any standard, version 1 moved onto using Collections+JSON in our case, however I didn't know better and didn't use ;version=0 to denote version info in my case).

In any case, the entire project plus the test case is basically a set of code examples that can be adapted by Plone to make use of. For the most part this seems to work well enough for the project using that.

[tisto]

This issue is related to plone.rest. Closing it here.