On 9 Mar 2006, at 18:28, James M Snell wrote:
That's an option, but I shouldn't have to parse Atom just to get a URL
when an HTTP response header would work.
I suppose its a choice between having to invent a header for each of
the metadata elements that can appear in an entry (which could be a
lot given all the use cases that are bound to come up), or just
returning an entry.
For example as Aleksander Slominsky just recently pointed out, he
would like to edit the metadata of media collections. In order to do
this the header would also have to include a link to the edit
location of the entry. And perhaps we should also return the id of
the entry in the header too, just so that the server know the
relation between this id and the media resource just posted, without
having to search through collections.
Since a blog editor is posting the media resource, it should have all
the tools to parse an entry...
Henry
- James
Henry Story wrote:
Why not just make it normative to return the entry metadata in the
body?
