Windows ME TCP woes with Rugby
[1/3] from: koopmans:itr:ing:nl at: 6-Aug-2001 13:20
Hi,
As you may know I have implemented a simple request broker for Rebol, Rugby (rugby3.r
in the script lib).
While testing some more I noticed that the client part under Windows ME has some problems,
it sometimes doesn't read anything at all. The server part may be running on any machine,
on any platform.
You can observe the effect on Windows ME by starting two consoles and type the following:
do read http://www.reboltech.com/library/scripts/rugby3.r serve [echo] ;in console 1
do read http://www.reboltech.com/library/scripts/rugby3.r rexec [ echo "Duh"] ; in console
2
On linux, NT4, 2000, Solaris: no problem.
My question: does it go wrong on any other platform?
This is what rugby-server does: it opens a server port in direct and no-wait mode. It
then accepts connections, set the mode to no-wait, reads the message, does it, and writes
back. As soon as the message is written, it closes the port.
The client does an open/direct, sends a message, and reads the result with a blocking
copy unless otherwise told.
Any ideas?
--Maarten
[2/3] from: g:santilli:tiscalinet:it at: 6-Aug-2001 19:26
Hello Maarten!
On 06-Ago-01, you wrote:
MK> While testing some more I noticed that the client part under
MK> Windows ME has some problems, it sometimes doesn't read
MK> anything at all. The server part may be running on any
MK> machine, on any platform.
I have had a number of problems while developing REBOL Chat on
Win98. First of all, it allows two processes to bind on the same
port. So, if you start the server twice you get unpredictable
results.
I also experienced other oddities, so I believe Win95/98/ME TCP/IP
stack is simply broken. But maybe it is just me.
Regards,
Gabriele.
--
Gabriele Santilli <[giesse--writeme--com]> - Amigan - REBOL programmer
Amiga Group Italia sez. L'Aquila -- http://www.amyresource.it/AGI/
[3/3] from: koopmans::itr::ing::nl at: 7-Aug-2001 12:23
Hi Gabriele,
I just got an email that someone has the same problem under Linux.
ANd it is strange that this is a problem under Windows, while a lot of other
software just works when using TCP/IP!
I am looking into it and I'll post things as they develop.
Thanks,
Maarten