News for hackers. Stuff that matters.
Re:QUIC, a multiplexed stream transport over UDP by corysama on Monday June 01, 2015 @01:11PM (#9640309)
IIRC, packets on different "channels" in enet don't block each other. So, a troublesome reliable packet that needs retransmitting unusually many times won't hold up packets on other channels -reliable or not.

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.

Re:QUIC, a multiplexed stream transport over UDP by Scramblejams on Monday June 01, 2015 @01:24PM (#9640447)
I was referring to their non-thread-safe (within a single ENet instance) architecture combined with the need to block if you want to pick up a packet the moment it arrives. I have to block to receive that packet, but while I'm blocking, I can't send a packet (because ENet isn't thread safe). Now, it will let you set a receive timeout, but then you just spend a lot of time spinning.