that is a very interesting question and unfortunately i don't have an
answer yet (this discussion is going on at the spec list now too)
I -think- and -assume- that a Content-Type header (application/json
for json, and application/atom
+xml;type=entry for atom) is intended to indicate the input format
type ...
But since this isn't clearly defined in the spec, i can't say for
sure. Hopefully the spec will be updated to clarify this soon.
-- Chris
On Jul 17, 2008, at 7:09 PM, Tamir wrote:
>
> RESTful API Specification says that the container must support dual
> representations for each resource. (Atom & JSON). What about HTTP
> method such as POST, PUT or DELETE that change data?
> The single example i found for such a request was an example about
> Batching:
> --------------------------------------
> POST /batch-proxy HTTP/1.1
> ...
> POST /people/@me/@all HTTP/1.1
> ...
> ...representation of new Person elided...
> --------------------------------------
>
> What is the format of the Person MAY be? Atom, JSON or both?
>
> Cheers
>
> Tamir Zaslavsky
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Implementing OpenSocial Containers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/opensocial-container?hl=en
-~----------~----~----~----~------~----~------~--~---
