[Cosmo-dev] atom media creation/update

[Brian Moseley]

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

> I usually use Firebug for this kind of thing, so it's not a huge win
> for me. Then again, it could be nice to do spot checks on
> subscriptions by just typing them into the browser bar, a situation
> for which Firebug doesn't currently help.

right. that's the situation i was suggesting. as a server developer, i
can't use the browser as a debugging tool with atom representations
(cos the browser hands them to my feed reader), but with xhtml ones, i
can.

> Just so we're clear: you're proposing that we leave everything except
> subscriptions and preferences _completely untouched_, correct? If so
> this doesn't sound risky to me.

no, i want to do this for items too. so where you are now creating an
atom entry document and POSTing it to the collection uri with content
type 'application/atom+xml', you'd instead just POST the eim-json data
to the collection uri with content type 'application/eim+json'. you'd
actually get to rm some code.

> We decided a while back that we need to have some facility for
> setting a preference in the CMP signup request to support the "signup
> and add this subscription to my account" workflow. Will this
> accommodate that?

the main suggestion is to change creates and updates to send media
rather than entry documents. this applies only to atom. however, the
xhtml representation of preferences could certainly be used by cmp.
for that matter, i wouldn't mind replacing all of cmp's custom xml
representations with xhtml ;)