Issue - Client session lost when browser minimized / background tab.
Documented new configuration option "useWorkerScheduler".
@@ -120,6 +120,17 @@ However, the second way allows you to pass other configuration parameters, curre
transport. Microsoft Internet Explorer 7 and 8 are known to limit the URI
length, so single large messages sent by CometD may fail to remain within
the max URI length when encoded in JSON.
+
+| useWorkerScheduler
+| no
+| true
+| Uses the scheduler service available in Web Workers via `Worker.setTimeout(fn, delay)`
+ rather than using that available via `Window.setTimeout(fn, delay)`.
+ Browsers are now throttling the `Window` scheduler in background tabs to save battery
+ in mobile devices, so the `Window` scheduler events are delayed by possibly several
+ seconds, causing CometD sessions to timeout on the server.
+ The `Worker` scheduler is not throttled and guarantees that scheduler events happen
+ on time.
|===
After you have configured the `cometd` object, the Bayeux communication does
