ports/buffering

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

Hi Christian, On Friday, June 21, 2002, 3:28:35 PM, you wrote: CL> Is there any information on how the REBOL ports buffering layer works? Did you try using /DIRECT? Just to see if it's really because of the buffering... (I think tcp:// ports are always direct anyway...) Regards, Gabriele. -- Gabriele Santilli <[g--santilli--tiscalinet--it]> -- REBOL Programmer Amigan -- AGI L'Aquila -- REB: http://web.tiscali.it/rebol/index.r

Gabriele Santilli wrote:

>Hi Christian, >On Friday, June 21, 2002, 3:28:35 PM, you wrote: >Regards, > Gabriele.