TCP/IP External for Windows 2000

[Dar Scott]

On Saturday, April 27, 2002, at 03:43 PM, Shao Sean wrote:

>> for a different feature set.
> mm.. considering you can write any feature that you require using 
> either the
> TCP or UDP protocols, i'm personally confused by what you mean..

Well, my needs are a little strange.  Here are some reasons I'm 
looking for an alternate way to do TCP/IP (say, external) for a 
while for Windows 2000.  The last one is very important to me.

1.
Revolution UDP lacks needed features to create certain kinds of UDP 
clients and servers, including those based on Internet standards.  
I got the impression from Scott Raney's comments on the MC list a 
couple days ago that this will be addressed in the next MC 
release.  Since the Revolution engine will lag behind this, it may 
be a while before this is addressed in Revolution.

Dar's priority:  Useful.

2.
As a generalization of #2, it would be good to be able to control 
or get all port data for UDP.

Dar's priority:  Important.

3.
And #2 can be applied to TCP.

Dar's priority:  Useful.

Those shortcomings below have been reported and I believe are still 
in the verification stage at Revolution.

4.
If a connection is not established on W2K (refused or no computer), 
the open callback is called and not socketClosed (as on OS X) or 
socketError making it hard to know when a connection is 
established.  For many applications that rely on a banner response 
this is not much of a problem, though.

Dar's priority:  Important.

5.
An established connection to a port on the same computer does not 
work (33%, 100%, & 100% of the time on three computers in my lab) 
on W2K.  Strangely, a user window operation (drag, minimize, 
resize) between close and the next open will fix this.  The first 
open always works.  This is characterized by no open callback and 
by write timeouts.  If anybody can point out something dumb I might 
be doing or a workaround, I'd be very pleased.

Dar's priority:  Acutely and painfully Important.


So...  I'm looking for alternate TCP/IP on W2K for now.  Since, I 
hope, this is temporary, something that works on W2K only is OK.

Dar Scott