Hello all,

I was recently reminded of network problems, such as a need to force the use of 
the "old network" on at least some Linux machines, and that I have had mixed 
results on Windows (not sure what is causing grief there, but suspects include 
2k3 vs. xp, bad network setup in general and ipv6 in particular).

So far, I have only one useful method that establishes a connection queue, then 
uses SocketStream to connect to is as locahost, enters a loop on 
#getConnectionOrNil, and then finally does some I/O.  As I said, results are 
mixed.

Another test that needs to be done is split the client and server across a real 
network.  I can do that (perhaps subject to weird constraints) between win2k, 
2k3 and Linux.  I tend to think of Linux as the client, but I might be able to 
flip that around.

My expectation (I can't believe I'm typing this<g>) is that Squeak will perform 
better than Pharo, only because of the "new network" changes, which I believe 
to be the cause of the problems.

I envision something like a friendly root kit: get each machine to download 
both Pharo and Squeak, and install a small .mcz into each image.  The idea is 
to allow many of us to try this on different networks and platforms, and to 
merge the results.

For remote testing, there would probably need to be a server class with 
start/stop methods, and the client side test methods would hopefully log what 
they can.  On successful remote conversation, the client should be able to 
automatically log details about the server, having read the details over the 
network.

Suggestions on how to build this would be greatly appreciated.  Can it all be 
done with Sunit, or is that asking too much?

Bill


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to