We aren't ignoring your situation, Adrian - Jeff and I are talking about how
best to deal with the situation and your offer to help. This revision will
indeed see some significant change in the oob/tcp component, mostly in the
init and connect procedures.
The concern is that we want to leave open
The changes we are planning to do will in no way preclude the use of
multicast for the xcast procedure. The changes in the OOB subsystem deal
specifically with how those connections are initialized, which is something
we would need to do for multicast anyway.
The routing method for the xcast is al
On Wed, Dec 06, 2006 at 07:07:42AM -0700, Ralph H Castain wrote:
> The concern is that we want to leave open the possibility of putting this
> revision into 1.2 since it will have a major performance impact on both
> startup time and the max cluster size we can support. The IP6 code is
> scheduled
