thunderpush
thunderpush copied to clipboard
Disconnect users - when used transport: xhr-streaming
When using transport : xhr-streaming - if you close the browser window and to make a request for the number of users (GET:/api/1.0.0/[API key]/channels/test) I keep seeing this user. The same thing happens when a user connects. In other words - there is no update. When using transpoprt websocket everything is ok. How can I fix it? Thank you very much!
So the server doesn't show the user disconnected? What version of thunderpush are you using?
I am using version 0.9.7. The server shows disconnected users, but with big delay. let me remind you that this only happens when using transport xhr-streaming. (when I use web sockets everything is ok)
Thanks, I'll do some research this weekend.
Thank you I will wait for any result
We're using sockjs-tornado for connection handling. The version we use is a bit outdated version (3.2.2) of the library at the moment. So we should probably first upgrade to 4.0.2 and check if the problem persists.
I've updated the tornado. At the moment I have 4.0.2 version. But the situation is even worse. Next: GET:/api/1.0.0/[API key]/channels/test - This query shows me all disconnected users. Additionally, do GET: /api/1.0.0/ [API key] / users / and I see a number of users (should be 0) GET:/api/1.0.0/[API key]/users/user_id shows me - true but although this user is offline The old version of the tornado was better.
The new version may contain some backward-incompatible changes, so upgrading may require us to rewrite some parts of our own code as well. I'll take a closer look at it.
We would like to work with this library (thunderpush) if you are able to provide any support I will be grateful
Good morning! After tested: All of the above problems occur when using a proxy server
additionally. If I use sockjs in the node (sockjs_chat-master) then the user is disconnected is displayed after about ~3 seconds
Did you have any luck in finding the reason for those delays? @mrStanislav
Unfortunately no ... there is another issue, the library does not work on Samsung Smart TVs... eg soket.io (nodejs) work