Slava,
Here's a simple test case on a localhost.
factor:
8000 <server> dup accept
xterm:
telnet locahost 8000
<manually close connection>
factor:
"hey" over stream-print dup stream-flush
! this doesn't produce an error. shouldn't it?
"hey" over stream-print dup stream-flush
! this time I do get an error:
! Error on fd 4: Broken pipe
! Debugger commands: ...
"hey" over stream-print dup stream-flush
! factor is now blocked.
Why isn't there an error message on the first send? Why does Factor block on
the third send? When Factor notices a "Broken pipe" error on a stream, should
Factor mark the stream as closed? Maybe this only makes sense for certain
kinds of errors. Perhaps it should be up to the programmer to catch errors
and mark the stream closed manually.
Ed
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk
