On 7/23/07, Katie Capps Parlante <[EMAIL PROTECTED]> wrote:
I don't think we've closed on a few decisions wrt handling icalUIDs. If I understand correctly, options available for Preview: A. Implement a restriction on the server where no collection has duplicate icaluids. Randy has the implementation ready to go. We'd also need: - Error message for clients that try to sync/publish collections with duplicate icaluids - Error handling in the desktop (it would be a sharing error for the collection)
I'm fine with adding the error handling to the desktop. We'll just need to have Cosmo respond with the "aliases" of the offending items, either in the response headers or body.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
