[Cosmo-dev] morse code docs

[Randy Letness]

Brian Moseley wrote:
> i've written up an initial draft of the morse code spec here:
> <http://wiki.osafoundation.org/bin/view/Projects/CosmoMorseCode>
Looks good.  Just a couple things:

1. "Delete Signifies that the indicated collection and all contained 
items are to be removed immediately from storage"
If we decide to use tombstones, this won't be the case.  Is this OK?

2. If we have to support locking, then we need to decide if we are going 
to support distributed locking (load-balanced cosmo), which is a lot 
more work.  Maybe for 0.6 we just support single server cosmo and tackle 
multiple server cosmo in 0.7 or later.

3. I touched on this on a previous email to you, but we need to figure 
out what happens when another client updates between a sync/update from 
the current client.  The use case is:

Client B does sync
Client A does sync
Client B does update
Client A does update

How does Client A get B's changes?

You mentioned we could require the sync token for an update, and the 
server would return an error if the token doesn't match up with the last 
sync, as in this case.  Client A would then be required to do another 
sync to get the updates from Client B, before sending its own updates.  
So this would end up looking like:

Client A does sync
Client B does update
Client A does update (gets error)
Client A does sync
Client A does update (no error)

-Randy