Implementing WebTransport datagram for volatile emit

[juanjaho]

Guarantees of actual delivery and order are core to the library's design, making it incompatible with a datagram approach.

However, with the introduction of WebTransport, specifically its unreliable datagrams, I believe there's a compelling case for reconsideration.

The existing io.volatile.emit() functionality in Socket.IO already signals an intent to send data without certain delivery guarantees.

It seems like WebTransport's datagrams would be a perfect fit for this particular use case, offering a more native and potentially optimized way to achieve that "fire-and-forget" behavior.

Would it make sense to explore how WebTransport datagrams could enhance or integrate with the existing volatile emission strategy?

Reference:
#5001 (reply in thread)