<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 09/03/2014 12:01 PM, Gilbert Martinez wrote: <blockquote cite="mid:CAOyHz4vWHwGqeyJ7PBGXHskGb24dP1O4M0H-WauiSEaDtQ5qpg@mail.gmail.com" type="cite"> <div dir="ltr">I'm having issues reading the response from a TCP server. Specifically, any attempt to read the input port does not terminate. I've used port->bytes, read-byte, and read-line. In all cases the effect is the same. <div> </div> <div>I thought that if there were no bytes available on an input port that the read attempt would just return <eof>. Is this some kind of exclusivity issue? Can I not read from the port until the connection with the server is closed or something? </div> </div> </blockquote> This is not true. Most functions like 'read-byte' block until there are bytes available to read. You don't get <eof> until the port (connection) is closed. If you want a non-blocking call, look at 'read-bytes-avail!*'. <tt>#lang racket</tt><tt> </tt><tt> </tt><tt>(define-values (in out) (make-pipe))</tt><tt> </tt><tt> </tt><tt>(thread</tt><tt> </tt><tt> (lambda ()</tt><tt> </tt><tt> (for ((i 5))</tt><tt> </tt><tt> (write-byte i out)</tt><tt> </tt><tt> (sleep 1))</tt><tt> </tt><tt> (close-output-port out)))</tt><tt> </tt><tt> </tt><tt>(for ((b in))</tt><tt> </tt><tt> (printf "~x " b))</tt> 'for' is pretty smart in my experience. I believe in this case it's using a sequence from 'in-port'. But in any case, you should see numbers print out before the port is closed. Does this help? Thanks, Dave </body> </html>