How the websocket bi-directional concept work?
Posted
by
GMsoF
on Stack Overflow
See other posts from Stack Overflow
or by GMsoF
Published on 2012-09-11T03:35:53Z
Indexed on
2012/09/11
3:37 UTC
Read the original article
Hit count: 166
I think the main difference between websocket and http streaming (I am not refering to polling and long polling) is websocket allows bi-directional communication which is similar to usual raw socket programming. (above is my understanding, could be wrong, feel free to correct me.)
My question is how the web client (browser) continue to send another request in the already-opened websocket? Usual http request will treat another request as new socket connection, but websocket does not, that is why I am confused, how it achieve that? It should be handled in Server side or Client (browser) side?
© Stack Overflow or respective owner