udt / News: Recent posts

http://sc06.supercomputing.org/news/press_release.php?id=14

We launched a new project, SECTOR (sf.net/projects/sector, sector.sf.net). It is a data space management system, which allows user to access files and data on distributed computer systems transparently, effectively, and efficiently.

SECTOR took most of my time and the udt-m and udt 4.0 progress has therefore been delayed. I will turn my focus on UDT as soon as the first milestone of SECTOR (release of SECTOR 1.0 beta) is reached.

http://www-unix.mcs.anl.gov/~bresnaha/udt_ref/

Please check the link above for the ANL version of UDT2 XIO driver.

The current UDT use a new UDP port (and 1 or 2 new threads) for each new UDT connection. Recently there have been increasing concerns for this design, when users need to handle firewalls and/or start many concurrent UDT connections. In response to this requirement, I will start a new branch of UDT, called UDT-m, which will use single UDP port and fixed number of threads, independent of number of connection.... read more

Thanks for your feedback on 3.0 beta. 3.0 final is now released.

next step? make it more reliable of course. Also, a group messaging protocol (GMP) based on UDP is going to be released. GMP can support message passing to any node without the overhead of connection setup/teardown of multiple TCP sockets.

The public CVS for UDT starts working again. You may check our most recent changes from CVS now. Note that there are some changes in CVS usage:

http://sourceforge.net/cvs/?group_id=115059

We just made a beat release of version 3.0. We are still testing it but we believe that it is good enough for a beta version.

For 2.x users, you should be able to transfer your application to 3.0 without any changes. However, before the final 3.0 release is out, we will still keep updating 2.x release. Right now we have a 2.4 version.

The v3.0 source code has been uploaded to sourceforge CVS. We are in alpha testing phase now. If interested, please check it out from CVS.

As promised previously, we added new SOCK_DGRAM to UDT to support partial reliable data messaging.

Support for congestion controlled unreliable messaging will be available in UDT 3.0! A message will have a time-to-live value. If the TTL expeires, the message will be discarded.

version 2.2 is released! this version includes several bug fixes from v2.1. Firewall punching ability is also included.

The most recent effort of the UDT development is to support firewall punching, especially those NAT firewalls. A preliminary version can be found in the sourceforge CVS area (no stable release yet). In this version we added rendezvous connection setup support.
Traditional BSD socket setup process requires explicit server side and client side. To punch NAT firewalls, a common method is to use the SO_REUSEADDR socket option to open two sockets bound to the same port, one listens and the other connects. UDT provides the more convenient rendezvous connection setup, in which there is no server or client, and two users can connect to each other directly.... read more

The new release fixed several bugs found in version 2.0. It also includes the beta version of the UDT/CCC (Composable UDT) feature.

The beta verison of Composable UDT is available thorugh sourceforge CVS. The Composable UDT allows users to define their own congestion control algorithms.

The final version of UDT 2.0 is released on Oct. 1, 2004.