Ws: WebSocket.terminate() vs WebSocket.close()
On readme:
// UseWebSocket#terminate()and notWebSocket#close().
There is this line. But it does not explain why, and I dived into the codebase and the issues but still could not find a reason. Can we include this information somewhere?
goktugyil
>All comments
ws.terminate() immediately destroys the connection, ws.close() waits for close timer to expire before destroying the connection if the other peer is not responsive.
Technically both can be used but ws.terminate() is better in that example (you don't want to wait another 30 sec before the websocket emits the 'close' event). Feel free to open a PR.
lpinca
on 23 Jun 2019
👍2
❤1
Was this page helpful?
0 / 5 - 0 ratings
Related issues
nabeelio
路
5Comments
brainkim
路
4Comments
ImBundle
路
3Comments
anonaka
路
5Comments
sherikapotein
路
3Comments
Most helpful comment
ws.terminate()immediately destroys the connection,ws.close()waits for close timer to expire before destroying the connection if the other peer is not responsive.Technically both can be used but
ws.terminate()is better in that example (you don't want to wait another 30 sec before the websocket emits the'close'event). Feel free to open a PR.