Am Dienstag, 27. Januar 2015 12:05:09 UTC+1 schrieb PMario:
- 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
Am Dienstag, 27. Januar 2015 12:05:09 UTC+1 schrieb PMario:
- 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
On Tuesday, January 27, 2015 at 2:06:48 AM UTC+1, NT wrote:
Regarding to the context of your seafile presentation:
1. Looks like you worked with tiddlywiki on node.js in seafile, since I
saw multiple separated files for each tiddler - did you (I did not yet,
only have read about)?
yes, it
Of course, separating data logic is a meaningful thing in most scenarios,
but that does not answer my current questions.
Ok, to be a bit more constructive some minds on sync from my side...
If we speak about distribution on file level (in the cloud) the question is
if it's neccessary to do
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
When I started tiddlydrive that was my goal. Currently the project is
frozen, but you can check it out at
http://danielo515.github.io/TiddlyDrive4Community Basically is a single
file HTML that syncs from and to google drive.
With all the little unresolved (and unresolvable) bits and
Am Dienstag, 27. Januar 2015 11:09:29 UTC+1 schrieb PMario:
2. That the inconsistent (conflict) file is brought up by seafile is nice,
but do you get noticed about that?
You don't. If you reload the page, you'll see, that there are conflicting
files. ... But TW doesn't have an easy
On Tuesday, January 27, 2015 at 3:53:50 AM UTC+1, Tobias Beer wrote:
I think with all these shared / collaboration concepts one thing is key:
separating the wiki(s) from the store(s)
right.
For collaboration around TiddlyWiki, the single-file paradigm is
essentially untenable,
The
Mario, please have a look at my comment to Tobias post as well. Thanks :)
--
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 tiddlywiki+unsubscr...@googlegroups.com.
On Tuesday, January 27, 2015 at 11:50:24 AM UTC+1, NT wrote:
Am Dienstag, 27. Januar 2015 11:09:29 UTC+1 schrieb PMario:
Page reload.
Sorry, I was speaking here about the seafile service and not about tw. But
I think you mean a page reload inside seafile as well. That's what I mean
is
2.1 Say you have 300 tiddlers aka 300 files - you'll not be able to
discover on your own when a new conflict file will appear among them. So do
you get a notice of the conflict?
Page reload.
No, that does not work.
--
You received this message because you are subscribed to the
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
- on sync side A:
-- use the TW5 autosave capabilities
On Tuesday, January 27, 2015 at 11:50:24 AM UTC+1, NT wrote:
Then is mobile use not possible on side B when on side A there is the
node.js version running with multiple files getting synced to A??
IMO not really possible
I am using TW apps for mobile access right now, but i am working
I'm sure there are quite some users, that would be happy with this
mechanism, because it has no dependencies. It's extremely simple. An if you
only did eg: 10 small changes in the text. Resolving will be fast too.
Yes, an improved manual importer makes total sense.
The problem here is,
Am Dienstag, 27. Januar 2015 12:08:44 UTC+1 schrieb PMario:
On Tuesday, January 27, 2015 at 11:50:24 AM UTC+1, NT wrote:
Am Dienstag, 27. Januar 2015 11:09:29 UTC+1 schrieb PMario:
Page reload.
Sorry, I was speaking here about the seafile service and not about tw.
But I think you
I don't see the deadlock with the information provided regarding the meta
information exchange.
If there is a syncfile from tw A for tw B, then tw B should delete it
after:
- the syncfile was recognized (tw B could check every 10 seconds) and
-- tw B updated itself according to the
I think with all these shared / collaboration concepts one thing is key:
separating the wiki(s) from the store(s)
For collaboration around TiddlyWiki, the single-file paradigm is
essentially untenable,
not just for the simple reason that to currently push 1 byte of changed
tiddler
you my need
Hey Mario,
I stumbled upon your post on the search for a possibility to realize a
shared/distributed work on a tiddlywiki in the cloud - not in the web -
with automatic syncing between teampartners who should be able to edit the
wiki at the same time (more or less). I think the problems are on
Hi Jonnan,
There are several file syncing services, that may work well with TW.
I did discover seafile [1] service lately.
They provide a file based sync, and are able to discover conflicts, if 2
files have been edited at the same time.
The mechanism doesn't do any automatic merging ...
19 matches
Mail list logo
