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 90.0.0.1
** Where: connect
** Near: port: open/no-wait url
I remember vaguely that 90.0.0.1 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.
> 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
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
