That is true. But it appears that encapsulating UDP sockets really has little sense. But I might be wrong.
BTW, I have a nice thing called "Urr", which stands for "UDP request-response", which is package that implements UDP based request-response (both Strings) proprietary protocol (adding realiability and allowing messages of any size to pass).
Maybe it could be useful for you? I was considering adding this public sources for a while...
cbpporter Messages: 1427 Registered: September 2007
Ultimate Contributor
luzr wrote on Fri, 20 November 2009 14:37
adding realiability
While I love reliability, UDP is by definition not reliable. I think any steps taken beyond a simple timeout would negate the benefits of it. Even the timeout is for some practical purposes overkill .
While I love reliability, UDP is by definition not reliable. I think any steps taken beyond a simple timeout would negate the benefits of it. Even the timeout is for some practical purposes overkill .
I guess it is more sophisticated than that.
For both requests and response <8KB, if there is no lost packet, there are only 2 datagrams going through with Urr (one to server, one from it). So no efficiency is lost.
Anyway, it happily handles all possible issues like lost or duplicated or long packets.