Good day folks,

I would like to employ a handler which continuously writes to the socket stream, so that the appended output becomes immediately available to the page viewer. Basically, I'm building a buildbot for CL libraries, and the build process can be long, so I want the feedback to be available as immediately as possible.

So, I look at PROCESS-REQUEST and I see that the handler returns before any output is written to the stream. My understanding is that I need to customize PROCESS-REQUEST, unless I want to take over header generation and can tolerate headers re-appended after my output.

The easiest way would appear to be subclassing REQUEST and providing a modified method for PROCESS-REQUEST. But it appears that this is impossible to do without affecting all handlers using the same acceptor, as the class of the request employed is the property of the acceptor -- as is mandated by PROCESS-CONNECTION -- which, again, dispatches on the acceptor.

So, there appears to be no way to customise hunchentoot in this regard, without changing its request processing workings.

Or am I just missing something?

regards, Samium Gromoff -- P.S. In case this sounds negative -- it wasn't so intended. Hunchentoot is a really great server!

_deepfire-at-feelingofgreen.ru O< ascii ribbon campaign - stop html mail - www.asciiribbon.org