Hi,
As I have witnessed in a web XMPP application, if a user closes browser window, they appear online in every one's roster as online for about another 30 seconds, before going offline.
Is this an issue caused by network latency or is this done purposefully by ejabberd? After a user closes their browser window, is there a way to further delay the unavailable/offline execution?
Thank you.
mhoang wrote: Hi, As I have
Hi,
As I have witnessed in a web XMPP application, if a user closes browser window, they appear online in every one's roster as online for about another 30 seconds, before going offline.
Is this an issue caused by network latency or is this done purposefully by ejabberd?
In the ejabberd source code file src/web/ejabberd_http_bind.erl there is a line:
-define(MAX_INACTIVITY, 30000). % msecs to wait before terminating
After a user closes their browser window, is there a way to further delay the unavailable/offline execution?
You can configure the mod_http_bind option max_inactivity. Search that in the ejabberd Guide.