[Cosmo-dev] atom media creation/update

[Brian Moseley]

On 6/11/07, Travis Vachon <travis at osafoundation.org> wrote:

> Now that I'm more on the same page, yeah, that doesn't sound like too
> much work on my end. That said, I'm not sure this will be a huge
> performance boost on our side, since the atom wrapper isn't really
> that big at the moment.

this one's not an issue of performance but rather of correctness. when
the client sends the server an entry, APP says that all of the data
specified in the entry elements, like author, summary, and updated
timestamp, are to be applied to the resource. the entry is not just a
meaningless wrapper but is in fact a representation of the resource
itself. but that's not actually how the server works today. it ignores
anything specified in the entry and simply applies the state of the
item as provided by the eim-json entry content. so, it's more correct,
and simpler, for us to use the media creation/update mechanism
provided by APP.