On Tue, 10 Jun 2008 12:25:22 +0200, Lars Rune Nøstdal larsnostdal@gmail.com wrote:
I tried to save a closure with the stream (returned from send-headers) in it and I was intending to call it later when the server has something it wants to push to that client. I'd let the thread that read the headers of the request originally "die out" opening a bit more room for other clients.
That won't work with the current code. Right now, the thread who gives the stream to you (via SEND-HEADERS) "owns" the stream and if you kill it, you can't just keep the stream.
You'll have to invent your own connection manager class for that. The exact plumbing of what happens when when requests are handled is still in flux, but I hope the current state will give you an idea.
..this might be too different from what HT currently does, or is. So maybe an option for me would be to add something that dispatches to this behavior internally (based on GET/POST parameters, I think) in HT. How close are you guys to finishing work on the branch by the way? I'm guessing it would make sense for me to work vs. the branch now.
It would definitely make sense to do this vs. the branch. Hans is currently on vacation and I'm busy with other things, so work on the branch has stalled a bit, but there should be more activity in the next weeks. No planned release date yet.