[REBOL] Read-io bug
From: ptretter:charter at: 13-Sep-2000 9:00
This is a multi-part message in MIME format.
------=_NextPart_000_0003_01C01D60.FFAE8FF0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
I finally realized it must be a bug in read-io that causes the Network
Timeout error message. Read-io is working fine as long as the server is
sending data to the client. The timeout occurs before any ping command is
sent from the server. I can detect from the read-io on the port when a ping
is sent from the server. There is nothing to explain the problem. To test
this I connected to IRC via Mirc and joined a channel called #rebolgods.
Then I activated the script to connect and join the same channel. The
result is a success and joins the channel. I can then query the nick and
send data to it and see the output in the REBOL console. However, after a
small amount of inactivity and before IRC send a ping the Network Timeout
error occurs. I have looked at the help and determined that I have utilized
the function correctly including the open function. It appears that some
other timing algorithim is not properly accounted for in the read-io
function. This also happend with the copy function on the ports data.
Since read-io is native I assume that it is using copy as an internal
function.
Paul Tretter
