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 mean a page reload inside seafile as well. That's what I 
>> mean is a problem.
>> 1. you have to do a page reload
>> 2. i don't think that you recognize one more file (the conflict file) 
>> among 300 other files in meaningful time without to get noticed by seafile. 
>> Do you get noticed be seafile??
>>
>
> No seafile syncs, but the nodejs server doesn't push this info to the 
> client. So the client needs to do a page reload, to see the changes.  
>
> How should seafile send a notice to the browser client. It doesn't know 
> about it. It's a file sync service. 
>
> -m
>
>
I think we're speaking about different thinks in this post. And I think 
it's a bit my fault because I have no clue about nodejs with tw.
The case I wanted to describe :
- a synced wiki in the cloud (single or multiple files not so important 
here)
- A begins a change
- B beginns a change
- A saves a change
- entire tw A or only one tiddler of it is synced
- B saves a changes
- entire tw B or only one tiddler of it is synced and overwrites the 
changes of A 
-> if we are lucky and have the right cloud service the version of A is 
saved as a conflict file by the cloud service and also synced to B

Thats what I understood from your hangout what seafile does. Do I got it 
wrong??
And then my question:
Does seafile notice me about the conflict or does it only deliver the 
'lost' version to me (I am B)?

-- 
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.

Reply via email to