The websocket packet headers are not going to get through to the user (except for maybe extensions), but we could make the data be a streaming kind of thing.
The main questions here are: How will it affect performance? Can we have two separate events for messages, e.g. message-stream, that emits when we have a message stream ready for processing and message, which gets emitted if an option is enabled and the message data is done collecting?
The websocket packet headers are not going to get through to the user (except for maybe extensions), but we could make the data be a streaming kind of thing.
The main questions here are: How will it affect performance? Can we have two separate events for messages, e.g.
message-stream
, that emits when we have a message stream ready for processing andmessage
, which gets emitted if an option is enabled and the message data is done collecting?