You're going to get conflicts when coda goes disconnected when the net
flakes.  You may want to change the wiki server to disallow starting
page editing in this case.  But they may be infrequent enough that
this is a net win, and this isn't intrinsic to coda - anything short
of application-level editing merging is going to have this issue.

You may also want to change the wiki code to not change web content on
read (counters).  One area where coda ends up not working well is when
there is application code to change read-read "conflicts" into
write-write conflicts.

An example is cfs (cryptographic filesystem) which by default opens
files for write.  Coda interprets [open-for-write read* close] as a
write, and sends the bits back to the server.

-- 
        Greg Troxel <gdt_at_ir.bbn.com>