On Tuesday, January 27, 2015 at 11:32:08 AM UTC+1, NT wrote: > > If somebody would ask me for a blueprint of file level syncing of TW5 in a > efficient but also simple way I would suggest the following: > - keep things simple with the single file approach - over disadvantages it > has many advantages >
Your description is OK, on a very high level, where every thing works, but the problem is in the detail. Like: "In theory there is no difference between theory and reality. In reality there is!" I'm just picking one "simple" detail: handshake - a session would mean here that you start with a synced wiki (copies) and > do handshakes by determining the name (convention) of the syncStatus file > considering the current cloud conditions > If you use your file based handshake, you need to sync the handshake = "lock file". ... But this is a "chicken / egg" problem. To trigger the "3rd party syncing action" you need to delete the lock file on side A. -> syncing is triggered, but doesn't work -> So you are out of sync. A thinks I'm ok B thinks A is still locked ... The problem here is the 3rd party transport. Because you can't trust it. So the locking mechanism needs to be more sophisticated. ... - after the sync the syncfile of A has to be deleted by B and A is not > allowed to write a new syncfile while the old syncfile exists > This is a typical condition for a "dead lock", where both sides are locked, because the "delete" action didn't work, for some unknown reason. -m -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
