Hi @Contente
I’ve posted an update to the topic you’re referring to:
Please check my reply there, I’ve attached the latest live_update.js as well as the demo package.
Some comments regarding your initial message:
You don’t need to have Scheduler or any other product running with node. Am I wrong on that one?
this is exactly right if I understand you correctly.
The main web app doesn’t have to be implemented in nodejs.
Live updates can work in a separate app schema , and only that app has to be done in nodejs.
Very simply, live updates are implemented the following way:
- You have your main web app which your users visit.
- You have a separate live-update app, which clients can connect to and exchange messages in real-time.
- On the web page, you connect the scheduler to this live update server.
- Each time the scheduler successfully saves changes to the database, it sends a message to the live update server which in its turn broadcasts it to all other connected pages.
- When the scheduler receives the message from the live update server - it applies the changes locally.
So the main app can work on any backend.
Technically, it wouldn’t be too difficult to implement the live update server on a different platform that supports websockets
Errors you encounter were caused by the fact that the live updates module on our site haven’t seen any updates for a long time,
so it has compatibility issues with both modern nodejs and dhtmlxscheduler.
If you try the latest files I’ve attached, it should work ok. We have a working live-update module for dhtmlxScheduler.NET, the module I’ve attached is a slightly modified version of that, ported back to Faye client.
I’ll duplicate the updated files I’ve attached in another topic:
live_updates.zip (1.6 KB)
scheduler-live-updates-app.zip (10.1 KB)