So you are going to want to associate and manage a pulse engine for each instance of your web client.
You can look at the explorer and how we wrapped up a thread that does this for a single pulse engine.
We are currently working on a scalable and dynamic multithreaded engine pool / management system, which would probably be exactly what you want. (when complete, I don’t have a timeline on when this would be ready yet). Currently this is not dynamic and not real time locked.
Basically, you need to manage (provide actions and pull data for your system) and advance time in each engine in some kind of threaded application. You would want to sleep the thread to maintain real time.
Take a look at the engine pool example. If you would like to take a shot, I can help review updates to help expedite this functionality.
You can run any of these how to examples on the terminal