Might want to implement some sort of heartbeat, keepalive, ping/pong etc

[anderspitman]

Currently the core features of omnistreams are:

• multiplexing
• backpressure
• works in browser (WebSockets)

Other nice ones:

• Supports both byte streams and discrete messages
• WebTransport-compatible wrapper available in the browser

I don't want to bloat it with features, but I'm seriously considering adding keepalives to the second list. The argument is anything robust build on top of omnistreams is going to need keepalives anyway, so why not build it in?

Maybe a consideration would be to see if WebTransport has any sort of built-in keepalive, and do what they do.

[anderspitman]

Maybe lean towards calling it "heartbeat" rather than "keep-alive", since with TCP I believe the problem is generally things crashing and not things like NAT tables expiring.