Hi Jeremy,
thank you for your detailed reply. The point is quite clear now. Years ago 
I developed a multi user database software an I know that the things about 
solid data locking and data exchange can become very tricky;-)  I wish you 
much success.

Regards
Oliver


Am Mittwoch, 9. September 2015 17:59:53 UTC+2 schrieb Jeremy Ruston:
>
> Hi Oliver
>
> There are a few areas that still need development work before TiddlyWiki 
> in the client-server configuration under Node.js is robust for multi-user 
> scenarios.
>
> The problem you've highlighted is that changes from one user are not 
> automatically pumped out to other connected users; they'll see the changes 
> when they reload the site, but they won't get any notification that 
> something has changed in the meantime. I favour using Server Sent Events 
> for the server to notify clients in real-time of changes.
>
> Another problem is that some state data will be shared between all users; 
> for example, the current sidebar tab selection. This problem is actually 
> ameliorated by the first problem: it would be much worse if state changes 
> were automatically propagated to connected users.
>
> Best wishes
>
> Jeremy
>
>
> On Wed, Sep 9, 2015 at 11:41 AM, rooster91an <[email protected] 
> <javascript:>> wrote:
>
>> Hi there,
>> I've got a question about using tiddlywiki with multiple users. There are 
>> many articles in the tiddliwiki group pertaining to this subject. But the 
>> more I read, the more I was stumped. So I hope you tiddlywiki professionals 
>> are not too much bothered with my further attempt.
>>
>> The idea is to run a tiddlywiki for a three person team, preferably 
>> served by node.js. Let's assume these three people open the wiki in their  
>> browsers, they look up and, from time to time, update information. My basic 
>> subject is how to avoid editing conflicts and overwrites. 
>>
>> In some articles was said, node.js-based tiddlywikis can manage this 
>> problem. In my basic setup, following the instructions on tiddlywiki.com 
>> the content can be overwritten by different clients. 
>>
>> How can I get this working? A simple warning like 'refesh your browser' 
>> would do it. Thank you very much.
>>
>> Regards
>>
>> Oliver Hahn
>>
>>
>>
>> -- 
>> 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] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at http://groups.google.com/group/tiddlywiki.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/955ce575-8cea-4805-ba08-0604f3401335%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/955ce575-8cea-4805-ba08-0604f3401335%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Jeremy Ruston
> mailto:[email protected] <javascript:>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0667d3ef-4574-426c-ac6d-20b778a369c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to