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)
Pros:
- avoid data on server that we'd need to change later
- work correctly with CalDAV clients for this case
Cons:
- more Preview work, at this point every code change introduces risk
- desktop experience for this edge case would be a little wonky
B. Change the desktop ical export behavior to not use uuids as icalUIDs.
Pros:
- avoid short term security issue
Cons:
- again more work, doesn't really solve the security problem
The two proposals are orthogonal, we can do either or neither.
I'll acknowledge that the discussion has been complicated by lack of
consensus that the current plan-of-record is the right long term
solution (at least on the desktop side), but everyone is pretty focused
on getting a wrap on Preview and not wanting to undertake a larger argument.
Anyone want to weigh in on the Preview decision?
Cosmo bug:
https://bugzilla.osafoundation.org/show_bug.cgi?id=9985
Earlier threads:
http://lists.osafoundation.org/pipermail/cosmo-dev/2007-July/004207.html
http://lists.osafoundation.org/pipermail/cosmo-dev/2007-July/004208.html
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
