Websocket batch processing / read completion event

[phraktle]

Describe the feature

Facilitate processing multiple available messages from a websocket in a batch. A possible solution is to provide a read completion event which indicates that all currently available messages from the network buffer were consumed.

Use cases

This allows improving latency in high-load / bursty consumers. For example, when consuming a real-time API with batch processing the consumer may skip messages to act only on the latest one in case of a burst / hiccup, effectively shedding load without introducing additional latency.

Contribution

Since the design has to consider feature interactions, such as back-pressure, I would request a core developer to look into this. Happy to provide support with review and testing.

[kovax]

I guess this could be available to any socket/streams.

[vietj]

@kovax that's right

[vietj]

I think the major work is define how that works with back-pressure pause/fetch/resume overall in a consistent manner