Project

General

Profile

Bug #11645

improve FWD Web Client ping-pong and timeouts

Added by Constantin Asofiei about 2 hours ago. Updated about 2 hours ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#2 Updated by Constantin Asofiei about 2 hours ago

In #11630 we found FWD can be improved when using cloudflare in front of the FWD Web client. Some notes:
  • Serban's findings at #11344-8 - the browser can throttle simple setInterval, thus ping-pong may not be performed.

The old value of 30000ms was dangerous because of this: https://medium.com/@adithyaviswam/overcoming-browser-throttling-of-setinterval-executions-45387853a826

  • we need to move the ping-pong to the FWD Java client side, so it does not rely on javascript to send it
  • we need to move the other setInterval usage (like for reconnect) to Worker threads

Also available in: Atom PDF