Followup, On Wednesday, August 18, 2021 at 2:03:53 PM UTC+2 PMario wrote: ...
> The function is called "syncFromServer". So if you open 1 wiki in 2 tabs > of a browser you will informed, if someone opened a tiddler. A _red_ "draft > of ... by <name>" button will be shown in the bottom of the wiki window. > The name will be only there if the username is set in the ConfigTiddler! > The server sent event plugin triggers the exact same mechanism. So it's possible to create instant feedback without the need to modify core functions. The disadvantage here is, that there is quite some overhead over the wire. The message flow is like this: 1) Server informs the client about new data 2) Client reads all the tiddler meta-data without the text field 3) Client compares all titles to see if something changed. 4) If something changed the client reads ALL tiddlers including text content 5) Client saves new data 6) TW UI shows new data. This workflow is OK for the current client implementation, since it runs on a client-side timer. But the with SSE it could be like this: - 1) Server sends the changed data to the client - 2) Client saves them 3) TW UI shows new data As you can see, there is a lot of room for improvements. Especially the "Conflict Free Replicated Datatype" that Joshua mentioned would be an interesting option here. -mario -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ac142d55-8998-41b5-9b72-863c2f922a20n%40googlegroups.com.
