search

tomatell / sipml5

Automatically exported from code.google.com/p/sipml5
0 stars 0 forks source link

onclose event not raised when websocket is closed #30

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
According to the standard, a browser must send 0xff00 to signal to the remote 
peer that it wants to close the socket. Chrome don't send this chucnk (buggy).
This is why we get 'Disconnected' message from sipML5 when the pending (ghost) 
connection is really closed by the server (e.g. activity) while the current is 
active.
Workaround: check if the closed event is from the active stack

Original issue reported on code.google.com by boss...@yahoo.fr on 29 May 2012 at 5:26