News for hackers. Stuff that matters.
Re:QUIC, a multiplexed stream transport over UDP by chetanahuja on Monday June 01, 2015 @10:54PM (#9643561)
"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."

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?

Re:QUIC, a multiplexed stream transport over UDP by boardwaalk on Tuesday June 02, 2015 @12:06PM (#9646783)
For my own use, games. For example, multiple objects moving: The message updating the position of one taking longer than another shouldn't block the other from being handled. Also, an object being moved over time: You only care about the latest position, within reason.

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.