Re: [AgileWiki] things are getting exciting: sharing

[Bill La F. <Wil...@Su...>]

Norm,

Well, for sure, synchronization doesn't work at web-scale. :-)

Actually, I was premature on much of what I wrote. Rebuild is a bit 
simpler than what is needed for sharing, though not that much. Rebuild 
processes everything at the time of occurence, not at the time the log 
file was received from another system--an important distinction.  Also, 
a create should be ignored if its parent has been deleted on the system 
where the log file is being loaded. So sharing is a bit more complicated.

Oh, and I've done a very superficial test of rebuild with the latest 
changes and it seems to run OK. Which is probably good enough for 
checkin right now, but fer sure it needs more testing before the weekend 
release.

Now, are you ready to start entering content? (I should know more by 
next weekend!)

Bill

Norm Kashdan wrote:

>Bill, you should be sure to emphasize that sharing is NOT synchronization.
>The Rolonic position on synchronization is simply that it does not work.
>Many systems have died trying.
>
>;-n
>
>-----Original Message-----
>From: com...@li...
>[mailto:com...@li...] On Behalf Of Bill la
>Forge
>Sent: Monday, June 19, 2006 2:07 AM
>To: com...@li...
>Subject: [AgileWiki] things are getting exciting: sharing
>
>I've just made a bunch of changes to TKS and Rebuild,
>though it will perhaps take a day for me to catch up
>on testing.  :-(
>
>But I wanted to let you know that we are very close to
>something quite exciting: sharing.
>
>What is sharing? Sharing is the exchange of selected
>log file entries between arks, where selection is
>based on Cabinet. It allows you to work locally in
>your own ark, but share the changes you make with arks
>on other systems, via RMI, svn or email.
>
>For sharing to work, we need to enhance the way
>rebuild handles destroys--it needs to destroy child
>rolons present in an ark which are not present in the
>ark which performed the destroy. That's not too
>difficult.
>
>We'll also want to tag the actions in the log file by
>cabinet, so we can just share the changes made to the
>cabinets which are being shared.
>
>Another change that we'll want is to have an
>incrimental version of rebuild which adds a log file
>from another ark to the existing ark without having to
>rebuild the entire ark.
>
>Sharing has been "in the works" for several years
>now--some prior versions of AgileWiki already
>supported this, so I'm quite familiar with the issues
>involved.
>
>The advantage of sharing is that you can work off-line
>(think laptop) and then share your changes when you
>come back on-line. And even when you are on-line, if
>you are making a lot of updates (think power user),
>things will go a whole lot quicker if you make the
>changes locally and then batch the updates to remote
>systems. Sharing is one of the major features targeted
>for AgileWiki3.
>
>Bill
>
>  
>