{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"open","user":{"avatar_url":"https://secure.gravatar.com/avatar/d7a1a921ca69a469d9e91b6bd5fac43b?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"d7a1a921ca69a469d9e91b6bd5fac43b","url":"https://api.github.com/users/erickhsiao","login":"erickhsiao","id":172891},"milestone":null,"labels":[],"assignee":null,"updated_at":"2011-11-07T15:24:57Z","comments":3,"closed_at":null,"url":"https://api.github.com/repos/igrigorik/em-websocket/issues/67","body":"not sure where does the problem comes from, but we tested whatever chrome, firefox or android..\r\nthe issue comes when the client lose internet, em-server would not receive event as \"ws.close\".\r\nso the connection still alive and would never destroy by anyone... \r\n\r\nIs there any event that I can get notice when user lose connection?  thanks.","html_url":"https://github.com/igrigorik/em-websocket/issues/67","number":67,"title":"Have no event when client disconnect ","id":2161065,"created_at":"2011-11-07T10:08:28Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/a17f0025641b4be419a6cd3845e55dd2?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"a17f0025641b4be419a6cd3845e55dd2","url":"https://api.github.com/users/igrigorik","login":"igrigorik","id":10652},"updated_at":"2011-11-07T15:24:57Z","url":"https://api.github.com/repos/igrigorik/em-websocket/issues/comments/2654709","body":"Which versions of FF and Chrome? Websocket spec is still a moving target so different versions of browsers implement different versions of the spec. EM-Websocket tries to abstract all that, but its possible we're missing some edge cases in some of the handlers.\r\n\r\ncc @mloughran: have you guys seen this behavior in production at pusher?","id":2654709,"created_at":"2011-11-07T15:24:57Z"}}