I reduced the already serialized requests to a sleep of 0.1 seconds and it’s still working.
For our unserialized AJAX WebIf->Server->Bridge requests we will implement some kind of blocking locks on the server side, saving a hires timestamp of „Bridge request Running since“ and „Last Bridge request finished at“ to slow down and serialize the Ajax requests. It‘s tricky to implement (also to handle filesystem locks and deadlocks on the server side).
Would be great to accept eg 5 concurrent http connections and queue them on the bridge side, making everything more easy.
And at least after sending the Bridge response, the current single connection should be available again, to not play around with delays/sleeps.