<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi, Elliott</div><div><br></div><div>Sorry again for late response, but I think I've found the reason about this issue: WAIT-FOR-INPUT correctly detected that there're inputs on the server side socket, but due to a subtle bug when updating the STATE slot of the socket object, the socket wasn't marked as READY, so when W-F-I was called by (READY-ONLY T), a empty list returned (and your code have no chance to get touch with the stream behind the socket, and nothing could be output ...)</div><div><br></div><div>Due to some problems on USOCKET SVN, I cannot commit my work right now, but I have a patch as .diff file in attach, which could solve all your needs. I hope you can take a little download it and apply to your local USOCKET directory and see if your application work well this time.</div><div><br></div><div>The bug you reported also affect ECL on Windows, but I don't sync my patch to ECL until I get your positive confirmation.</div><div><br></div><div>Regards,</div><div><br></div><div>Chun Tian (binghe)</div><div><br></div><div></div></body></html>