Eric Scheid wrote:
That's bugged me too. If posting a binary to a media collection results in an Atom Entry being created which references the binary, why can't the Location header point to the Atom Entry in the first place ... at least the client can then use that to find everything else they need.
Ah, but that's not what happens. When a binary is posted to a media collection, no persistently-referenceable Atom entry is created. One is included in the feed used to enumerate the members of the collection, but that is not independently referenceable the way an entry collection member is... nor is it clear where any of the metadata contain in that entry actually comes from or how it correlates back to the original post. therefore, Location always just points to the binary and everything else is left as an exercise for the implementor.
- James
