Re: sockets are not really ports?

[Brad Knotwell <knotwell at ix dot netcom dot com>]

Jim Blandy writes:
 > 
 > > While implementing the server side of HTTP, I have come across three
 > > annoying things:
 > > 	accept blocks all threads
 > > 	select won't take a socket port
 > > 	set-current-input-port won't take a socket port

I don't know about the first and last one, but my ftp library works
fine using select on a socket (guile v. 1.3.4 and 1.3.2; OSes: FreeBSD
and Linux).  

 > All of these ought to work fine, so I think they're all bugs.
 > 
 > Hopefully Gary Houston or Mikael Djurfeldt will jump in with a patch
 > for this.  I don't really understand the internal select stuff.

--Brad