x/net/websocket: messages not exposed in package API #7632
Description
WebSocket peers exchange messages. A message is composed of one or more frames. The (*Conn).Read and (Codec).Receive methods return a single frame. There is no mechanism to detect message boundaries or otherwise compose frames into a message. To use this package, an application must provide its own framing or assume that the peer sends single frame messages. My guess is that most applications assume that the peer sends single frame messages because that's what browsers and the websocket package do. This assumption is not true of all peers.