{"action":"closed","issue":{"url":"https://api.github.com/repos/miguelgrinberg/Flask-SocketIO/issues/114","labels_url":"https://api.github.com/repos/miguelgrinberg/Flask-SocketIO/issues/114/labels{/name}","comments_url":"https://api.github.com/repos/miguelgrinberg/Flask-SocketIO/issues/114/comments","events_url":"https://api.github.com/repos/miguelgrinberg/Flask-SocketIO/issues/114/events","html_url":"https://github.com/miguelgrinberg/Flask-SocketIO/issues/114","id":76063749,"number":114,"title":"Delay between client disconnect and server handling of disconnect event","user":{"login":"hexturtle","id":9427813,"avatar_url":"https://avatars.githubusercontent.com/u/9427813?v=3","gravatar_id":"","url":"https://api.github.com/users/hexturtle","html_url":"https://github.com/hexturtle","followers_url":"https://api.github.com/users/hexturtle/followers","following_url":"https://api.github.com/users/hexturtle/following{/other_user}","gists_url":"https://api.github.com/users/hexturtle/gists{/gist_id}","starred_url":"https://api.github.com/users/hexturtle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hexturtle/subscriptions","organizations_url":"https://api.github.com/users/hexturtle/orgs","repos_url":"https://api.github.com/users/hexturtle/repos","events_url":"https://api.github.com/users/hexturtle/events{/privacy}","received_events_url":"https://api.github.com/users/hexturtle/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/miguelgrinberg/Flask-SocketIO/labels/question","name":"question","color":"cc317c"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-05-13T17:32:09Z","updated_at":"2015-05-14T17:53:17Z","closed_at":"2015-05-14T17:53:17Z","body":"I've noticed there is a significant delay between when the client navigates away from my web app and when the server receives/processes the disconnect event. My guess is this is really an issue with using an older version of the Socket.IO client, 0.9.16. Though, if this is not the case, I would greatly appreciate guidance for how to solve this.\r\n\r\nNevertheless, the documentation says this is the most stable version of the Socket.IO client:\r\n> The 1.x releases of the Socket.IO client-side Javascript libraries are not compatible with project gevent-socketio. At this time the Socket.IO client release 0.9.16 has been found to be the most stable.\r\nhttps://flask-socketio.readthedocs.org/en/latest/\r\n\r\nI tried using the latest version of the Socket.IO client as well, but encountered errors as expected.\r\n\r\nWith that said, I don't know if the latest version of Socket.IO addresses this issue. But version 0.9.16 does not appear to do so. Therefore, I believe this issue can be attributed to Flask-SocketIO's lack of compatibility with newer versions of the SocketIO client.\r\n\r\nIf anyone has found a way to fix this, or if I'm totally off base with identifying the cause please let me know."}}