JIC you haven't seen it, it covers some of the bases: http://enet.bespin.org/
IIRC I got frustrated with its (at least at the time) inability to send a packet while waiting on a packet to be received so I gave up and started writing my own spin on RFC 908.
Edit: from the docs
> To combat this latency and reduce the ordering restrictions on packets, ENet provides multiple channels of communication over a given connection. Each channel is independently sequenced, and so the delivery status of a packet in one channel will not stall the delivery of other packets in another channel.
I found this issue which looks related to your problem: https://github.com/lsalzman/enet/issues/23
An issue there describes a hack (sending a packet to your own socket to wake up enet_host_service). Not a terrible hack and much like the "self-pipe" trick.
And there's also the fact that I want something that runs on the BEAM VM...
What's the use-case you're thinking of exactly? Why "optional" reliability and ordering? What are the cases when you'd use the reliability and when not?
There are other models of simulation that aren't as loose (lock step-style for example).
Other messages would not be unreliable/unordered. Important state changes, chat messages, etc.
I know voice and video applications can cope with lost packets as well. This is in fact what SCTP was built for.
I really wish there was a solid "TCP replacement" with optional reliability, optional ordering and multiplexing that I can run over real networks as user level code, among other features. But the view from the ground from what I've seen is that people either use TCP or build their own protocol that runs over UDP (I'm thinking about games specifically here).
Am I missing an option here? Maybe I should dig into libquic and really figure out how to use it and if it can do what I want.
[1] https://github.com/devsisters/libquic [2] https://code.google.com/p/sctp-refimpl/