[Cosmo-dev] This and Future issues

[Brian Moseley]

On 8/9/07, Randy Letness <randy at osafoundation.org> wrote:

> No I was thinking request parameters like in the URL so that the
> protocol layer has access to them (like in the time-range queries).

we can't use query string parameters when PUTing a resource, tho we
could potentially include information in the uri-path, eg
/item/{master uuid};{modification uuid}, but that's both a
complication and a perversion of the item resource imo.

if we have to change something at the protocol layer, here's my
suggestion. the uri /detached/{master uuid};{modification
uuid}/{projection}/{format} identifies a "detachment resource". PUT to
that uri creates the new item, updates the old item's recurrence rule,
and moves modifications to the new item as necessary. the response is
a feed with two entries, one for the old item and one for the new
item.

> Thinking about it more, we only need a single parameter, which is the
> uuid of the occurence or modification that the user is editing.  That
> gives us the parentUuid and the last recurrenceId.

we should be treating modification uuids (all uuids, really) as opaque strings.