Aleksander Slominski wrote:
> hi,
>
> what is the best practice (interpretation of APP) for including
> <atom:entry> entity in 201 Created HTTP response to POST of new resource?
> is <atom:entry> entity required for media collections? especially when
> Location points to binary content? this is very confusing as in
> draft-08 there are two different examples: section 8.1.1 vs. section 12?
>
Optional. There is a proposal on the table that says if a response
entity is returned, it should be an atom entry.
> is it allowed to POST atom:entry with binary content to media
> collection? [1]
The media resource created would be an Atom entry document.
>
> for entry collections: is it allowed that <atom:entry> POSTed has no
> atom:id so the atom:id is assigned by server? in that case should
> <atom:entry> be returned in 201 Created response to let client know that
> it needs to update its representation of atom:entry (and get required
> atom:id)?
>
The atom entry MUST be valid... meaning it must have an atom:id. Our
implementation ignores the incoming atom:id and replaces it with our own id.
> how are current implementations of APP dealing with it?
>
> are there available captures of HTTP traffic for perusing (something
> like [1])
>
Later tonight I'll capture some traces and post 'em.
- James
