Hacker News Reader

Am I mistaken in my understanding that WebSockets is a stateful protocol? If your problem maps well to resource oriented architecture, when would the benefits of switching to this outweigh the fact that you'd be giving up response caching and scaling on a per-connection basis?

View on HN

WebSockets are sockets with a very small bit of goop layered over them. In terms of the state you are talking about, they basically have the same amount of state as a TCP socket, which itself is mostly "connected" or "not connected". So the question of the "statefulness" of websockets, in the sense you mean, is ill defined, because statefulness is or is not added by higher layers, just as with TCP sockets.

Reply on news.ycombinator.com