On Friday 18 November 2005 07:23 am, Greg Troxel wrote:
> You're going to get conflicts when coda goes disconnected when the net
> 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.

Since I haven't installed a wiki, I may not make any sense .... but let
us assume that one can do the following following things:

    a) All read pages are set up with relative paths so that any
       web server can serve them.
    b) Any write of data be directed at one server.  (Assuming that
       writes are much less frequent than reads and can stand the
       long RTTs.)

  So the Coda server is "near" your "primary web client".  That client
would serve both the read and write functions of your web site.

  Then, you can set up coda clients at other points to be the "mirrors"
and serve the same pages.  You could hoard the entire site at the
"mirror" servers and then it would keep the site in the cache.  Since
writes go to the primary web site, you would have a much lower chance
of having conflicts.   This does have the side effect of making writes
unavailable if one can't get to the primary web site, but the rest of
the site should be available.

  You could have as many of the read sites as needed.

  --Phil

-- 
Phil Nelson                       NetBSD: http://www.NetBSD.org
e-mail: phil@cs.wwu.edu           Coda: http://www.coda.cs.cmu.edu
http://www.cs.wwu.edu/nelson