Ack ic. I never even thought of that one. Although, I'm wondering how
likely this is and whether it's a big deal if we don't have a
solution for this in the Preview timeframe?
I've pulled together a wiki page to keep track of scenarios and
possible solutions:
http://wiki.osafoundation.org/Journal/ReadOnlySecurityHoleScenarios
On Mar 15, 2007, at 4:19 PM, Morgen Sagen wrote:
Well, I mean the following:
User A publishes collection C1 and C2; A puts event E1 into C1, and
puts event E2 into C2
User A gives user B a RW ticket for C1
User A gives user B a RO ticket for C2 (because he doesn't want B
to edit E2)
User B subscribes to both
User B copies E2 into C1, modifies E2 and syncs
User A syncs and sees the change to E2 in C1 (and also in C2)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
