That's interesting. We ran into a problem here which I had to fix by changing the default value of the read-only keyword parameter of wait-for-input from nil to t.
I got some explanation of wait-for-input from Erik Huelsmann, who designed this stuff. I sent him back some suggestions and questions, but I don't think I got an answer. The real question is whether Hunchentoot is interacting properly with usocket.
I haven't checked to see whether we are currently using the very latest usocket library here.
Andrew Pennebaker wrote:
The "New York version" (hunchentoot:start (make-instance 'hunchentoot:acceptor :port 4242))
creates a stalling web server, never loading, never error'ing.
When I remove the code :ready-only t from line 377:
(when (usocket:wait-for-input listener :timeout +new-connection-wait-time+)
The New York version works fine.
Specs:
* Hunchentoot 1.1.1 * Quicklisp * CLISP * Mac OS X
tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel