Jump to: navigation, search


Tuning the CometD timeout interval to optimize chat channels for mobile device activity and for notifications

When people use their mobile devices, they often need a longer chat timeout interval than they do for their laptops. For example you might start a chat and then:

  • Lock your screen for a minute or two
  • Switch to another application before you resume your chat

Given that the default value for CometD's maximum timeout interval is 15 seconds, these everyday patterns of mobile device usage can cause your customers to experience unexpected disconnections when you use the Web Engagement Chat Widgets in scenarios involving mobile devices. Although a 15-second timeout interval can be just right for dealing with unstable networks, Genesys recommends that you consider increasing this value to something like 120 or 180 seconds in order to avoid these mobile-related problems.

You can also adjust this interval in situations where your network is experiencing significant delays, since Web Engagement uses CometD as a channel for notification messages.

Note: It is also important to avoid overly large values for this option, which can adversely affect memory consumption and performance on the server side.


Comment on this article:

blog comments powered by Disqus
This page was last modified on September 19, 2017, at 15:05.