[Cosmo-dev] atom media creation/update
travis at osafoundation.org
Mon Jun 11 11:24:05 PDT 2007
>> 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.
I think this sounds correct in the long run, but I'm a bit worried
about adding work at this stage in the game for preview. While I'm
sure the code would actually shrink, as this seems simpler, it would
also require another round of running through the code and working
out the various implications and implementation details. I'm
certainly not afraid of this work, and given the likely performance
improvements I think it would be fun and satisfying, but I am
concerned about adding another 3-5 days worth of work on this end.
>> 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 ;)
Also probably correct in the long run, but I just want to make sure
that setting preferences as part of the signup POST doesn't get
dropped on the floor for 0.7. Putting it on the chopping block is
fine in my book, but the floor would be a bad place to be ;)
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
More information about the cosmo-dev