UDT is not a replacement for TCP or UDP - it is a data transfer protocol built on top of UDP, with some additional TCP-like features to aid in data integrity (negative ACKs to be specific). I've never used UDT, so I can't speak specifically about it. In general, though, my feelings on technologies like this is that they're great to consider, if and only if they would solve a specific problem you're having. This isn't something you'd want to put into production just for the fun of it. If you have a very high-speed network, say 10Gbps+, and you're schlepping a *lot* of data around, it may be worth implementing. On Fri, Mar 1, 2013 at 11:26 AM, Brian Wood <woodbrian77 at gmail.com> wrote: > Does anyone have experience using UDT? > http://udt.sourceforge.net/ > > Did you replace TCP or UDP with UDT? > Someone suggested I consider using UDT, so > am checking into it. Currently I'm using both > TCP and UDP -- TCP between my back and > middle tiers and UDP between the middle and > front tiers. I guess I could use UDT to replace > either or both of those uses. Tia. > > > -- > Brian Wood > Ebenezer Enterprises - John 3:16. > http://webEbenezer.net (651) 251-9384 > > > > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20130301/b170d2b0/attachment.html>