Hi,
Using the same OSC for both the RR-WorkerThreads and long-response background
threads may result in deadlocks in a heavier load scenario (which is bad for
your karma)
Using en extra OSC for every background task may consume too much memory.
Fortunately there exists the combination of ERX
Hi there,
looks like the main cause of those overlapping R/Rs which we ar clashing with
lately is that some users just open their session in more windows or tabs, and
work concurrently in those. Sigh.
It's self-evident why it is a pretty bad idea from the technical POV, but I am
afraid we can'
Hi OC,
This is a very complex question with many possibles solutions having their owns
problems...
If you use auto-magic WO with auto generated url using actions bindings with
complex pages, there is no safe way to support multiple concurrent tab or
windows in the same browser for these compon
