[Cosmo-dev] Re: securing access to items in multiple collections

[Brian Moseley]

On 9/28/07, Morgen Sagen <morgen at osafoundation.org> wrote:

> Could the client just include the list of all tickets it has
> associated with the particular server, rather than trying to compute
> the subset of tickets based on which particular items are being
> synced?

this is playing pretty fast and loose with tickets. it would allow a
ticket issued on collection B to apply to an item republished from
collection A. not what we want.

i'd think that if a user is copying an item out of a subscribed
collection, you'd just store that collection's ticket along with the
new relationship between the item and the collection it's copied into.
then you could send that specific ticket along with that item's
recordset when publishing the destination collection.

> At least for the short term, I would say that if any of the items
> being sent to the server fail because of improper access control the
> entire operation should be canceled atomically.  Having partial
> success for a sync is not something Chandler supports right now;
> currently when an error occurs, we cancel the entire transaction.

that's fine. we can come up with a response that communicates "this
request might have succeeded but there was an access denied error for
item <uuid>".