Pretty much, websocket implementations usually handles the buffering part so you really only need to handle "full" events. Easiest example is probably games, e

Pretty much, websocket implementations usually handles the buffering part so you really only need to handle "full" events. Easiest example is probably games, events could be things such players moving to new locations, firing a weapon, explosions. In realtime games, as well as "request-response" scenarios, it's common to have some kind of response that acknowledges that data was received.