You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use "long" requests and my own server-side implementations for the login/poll/post handlers.
At the end of every "poll" request (after 30 seconds) I wanted to send the whole contact list to the client with current statuses of all users. So I added a "status update" message for every user in the contact list. But because AjaxIM doesn't check status CHANGES on client side, i get an output like this in the chat window:
05:28 PM - user became available.
05:28 PM - user became available.
05:29 PM - user became available.
05:29 PM - user became available.
05:30 PM - user became available.
05:30 PM - user became available.
I think status CHANGE checks should be implemented on client side. So if user x is already online and a "status update" message was sent as response to the "poll" request, the new status should only be shown if it really changed.
The text was updated successfully, but these errors were encountered:
I use "long" requests and my own server-side implementations for the login/poll/post handlers.
At the end of every "poll" request (after 30 seconds) I wanted to send the whole contact list to the client with current statuses of all users. So I added a "status update" message for every user in the contact list. But because AjaxIM doesn't check status CHANGES on client side, i get an output like this in the chat window:
05:28 PM - user became available.
05:28 PM - user became available.
05:29 PM - user became available.
05:29 PM - user became available.
05:30 PM - user became available.
05:30 PM - user became available.
I think status CHANGE checks should be implemented on client side. So if user x is already online and a "status update" message was sent as response to the "poll" request, the new status should only be shown if it really changed.
The text was updated successfully, but these errors were encountered: