ports, buffering and general weirdness
[1/4] from: chris::langreiter::com at: 21-Jun-2002 22:42
Is there any information on how the REBOL ports buffering layer works? I'm currently trying to track down weird problems I have with a hipe-inspired REBOL server - "usually" it works very well, but when there's a bit of other network traffic on the machine (Win2K), e.g. I open a web site, client ports start to killed (none is received on the client side - frankly I don't know if the client can't handle the incoming data fast enough or if it's a different kind of problem). Is this a symptom that's known to experienced server writers? If you want to try it yourself, you can download the package from http://www.langreiter.com/rebol/server/0.3.0/ Start the generic-server.r first and then client-run.r, in the client-run.r console enter "evertest". You can start several clients at once as well. I would be very happy to receive reports on the behaviour ("port unexpectedly closed, retrying ..." is the evil message to be on the lookout for ;-). Best regards, -- Chris
[2/4] from: anton:lexicon at: 22-Jun-2002 21:27
This is what happens when I try it.
>> do %generic-server.r
synerge generic server 0.3.0 ; this doesn't match header (?) accepting connections ...
>> do %client-run.r >> evertest
** Access Error: Cannot connect to 188.8.131.52 ** Where: connect ** Near: port: open/no-wait url I remember vaguely that 184.108.40.206 is a local port, right? Overall, I would suggest starting a new project of client & server and building up again. I did that a couple of times. :) Networking bugs can be hard to locate, I'll say that. Anton.
[3/4] from: chris:langreiter at: 22-Jun-2002 15:34
> I remember vaguely that 220.127.116.11 is a local port, right?
Sorry, yes, you have to change the IP to 127.0.0.1 in client-run.r ...
> Overall, I would suggest starting a new project of > client & server and building up again. I did that a couple > of times. :)
A new project? How would that help?
> Networking bugs can be hard to locate, I'll say that.
So much I've found out as well ;-) -- Chris
[4/4] from: anton:lexicon at: 23-Jun-2002 0:43
Ok, I changed url to 127.0.0.1 I tested using win2k and latest view beta. Right, I just ran five clients and they each show the evil error message sometimes. I noticed that I can get each client to produce the error message very reliably if I click and hold the rebol console window scroll bar knob (to prevent it moving) for more than around 4 seconds. Sometimes this action causes some or all of the other clients to also wait, and then to also produce the error message. Hope that's useful. Anton.