5 ms·
I think you have missed the mark by such a wide margin that I need to call you on your bullshit. > I think what lots of people are missing is that Websockets d
by cenuij 15y ago
I think you have missed the mark by such a wide margin that I need to call you on your bullshit.
> I think what lots of people are missing is that Websockets doesn't compete with REST or SOAP, it competes with HTTP.
Websockets of any reference are implentations of HTTP, your lack of knowledge is not a badge of authority.
"Of course, this happens within a sandbox that involves initiating the connection over HTTP and tunneling the protocol through a server over port 80."
I am sure that you have no clue about what your talking about, I will bring this forward with the following statement:
"We're back to the days when anyone could and did develop their own protocols, and many of those became standards."
Your name is not on any IETF bodies or standards, who are you exactly?
- mahmud 15y agoI think you have missed the mark by such a wide margin that I need to call you on your bullshit. Not a good start :-|
- cenuij 15y agoyeah, it's a bad thing when tech beats bullshit :(
- deleted 15y ago[deleted]
- icebraining 15y agoWebsockets of any reference are implentations of HTTP As parent said, they only implement HTTP for handshaking. Then you switch to the websocket protocol. To quote websocket.org: The protocol switch from HTTP to WebSocket is referred to as a the WebSocket handshake. (...) The browser sends a request to the server, indicating that it wants to switch protocols from HTTP to WebSocket. (...) At this point the HTTP connection breaks down and is replaced by the WebSocket connection over the same underlying TCP/IP connection. The rest of your post is just argument-free personal attacks, therefore I'll refrain from replying to it.
- danssig 15y agoHe was right. Who are you exactly?