[Cosmo-dev] atom media creation/update

[Brian Moseley]

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

> That's probably true, but every time estimate I've made for this
> process has turned out to be dreadfully optimistic. Given that we're
> talking about changing the XML wrapper that the browser is in charge
> of interpreting, and given how unpredictable and difficult to debug
> browser differences often are, I'd say this is about right.

i think you didn't understand the proposal. it  deals with how the
client sends creates and updates (ie write requests), not with how it
reads responses (which is where the browser has to interpret xml).

looking at the itemToAtomEntry function in eim.js, it seems that you'd
just change it to this:


    itemToAtomEntry: function (object){
         return dojo.json.serialize(this.objectToRecordSet(object));
    },

then in Atom.js's saveItem and createitem, you'd set r.contentType to
"application/eim+json", and voila, you're done.

> Bug 8720, though I think where we left it was with me doing the CMP
> work. Things got a little confused because of the data format switch,
> so we should probably go back and rethink whether this one makes it
> on the schedule :)

ah, i'm not cc'd on that bug, which explains why i didn't know
anything about it.