@enq,
I don’t have an answer, but I am doing something similar and it is working … for now. I’m trying to formulate a question for I too am concerned about scope issues with threading etc. before I invest too much time 1
My application that is getting data from a telnet socket (streamed binary or text from some C applications.) I have a python thread (IO limited) that babysits these connections asynchronously, checks for data, unpacks it and stores it in various data-sets for the dash callbacks. It has a method that is used by callbacks to retrieve data (sensor data). This is streaming data, so I use the interval feature to trigger callbacks to update the graphs that use this data.
I’ve tried running the dash app in default (threading) mode and with threads disabled and processes=4. In both instances it works OK.
app.run_server(threaded=False,processes=4)
(I haven’t looked into whether I’m truly using multiple processes. And my C applets are indicating only one entity is accessing them, so I know that multiple telnet sockets are not being opened.)
I’ve opened some 10 clients (all on a local machine, this is running on a private network.) They all are showing the data as I would expect. Each client performs its own accesses to the thread that handles the interfaces (I see it being called each interval by each client) but this is accounted for in the design.
Sorry I couldn’t be of more assistance.
1 I’m working on an off-line lab equipment control and monitor. I’ve looked into various ways to be able to view my real time sensor information and Dash won among all the various options. I’m now concerned that it might not be suitable for a command and control interface…