morse code docs

About the implicit locking on updates:

If we do this, we will also have to implicitly lock the
collection on 
updates from CalDAV right?  Otherwise a CalDAV PUT could
sneak in some 
data during a morse code update.  This effectively
serializes updates to 
collections.  It shouldn't be a big performance hit as there
are very 
little simultaneous updates.  Just a change from what the
server 
provides now, which is simultaneous updates to a collection
assuming the 
updates are to different items.

-Randy
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On 11/20/06, Randy Letness <randyosafoundation.org>
wrote:
> About the implicit locking on updates:
>
> If we do this, we will also have to implicitly lock the
collection on
> updates from CalDAV right?  Otherwise a CalDAV PUT
could sneak in some
> data during a morse code update.  This effectively
serializes updates to
> collections.  It shouldn't be a big performance hit as
there are very
> little simultaneous updates.  Just a change from what
the server
> provides now, which is simultaneous updates to a
collection assuming the
> updates are to different items.

yes. in fact, i wonder if there's any reason for us to ever
*not* lock
the collection for any update via any protocol?
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev