> > - this doesn't use a client-server architecture. Given the questions I > have been asked this deserves to be said a few hundred more times. >
This to me sound more like the old Groove Networks database system was based. I feel that you really need to take a look at the Groove architecture as it does have possible implications which parallels what you are trying to achieve here. I kind of achieved something similar using TWC, when I created "worker" wikis. Each worker had their own TWC installation, and I used the SyncFileTiddlerPlugin ( http://tiddlywiki.abego-software.de/#SyncFileTiddlerPlugin ) to export a single tiddler which carried the actual work. This was replicated around via DropBox into the central wiki (mine) where I could see the changes and re-allocate the work out the the workers. It wasn't a true cross installation setup as each worker only saw their own stuff. In fact you could exact mimic such a setup with the TWC SharedTiddlersPlugin ( http://yakovl.bplaced.net/TW/STP/STP.html#SharedTiddlersPluginInfo ) simply by "including" the shared wikis of the other users in the network. But what you're trying to achieve goes far beyond this kind of system and I wish you well in it's implementation. -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b1f5313f-7bba-4483-8d3d-e111e1cc3e71%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
