A year ago or so, a few of you talked about integrating WK with Twisted.
Those discussions of last year revolved around various integration
levels: moving servlets to resources, for example, but at this point I'd
like to consider Twisted just as an adapter: writing an adapter in
Twisted to marshal a request and send it to a waiting AppServer, ala
mod_webkit et al.
I'd like to open that discussion again, because we're interested in
(occasionally) replacing Apache deployments with Twisted, but still
having WK behind certain parts of the URI tree.
Without digging much, it seems like it would mostly be easy; the CGI
adapter code can be adapted to twisted without too much effort, I expect.
But some theoretical questions:
1. Would this be a "Resource" or a protocol/factory?
2. Given that Twisted is async, and WK is not, what are ways to keep
twisted from blocking as WK runs a servlet? Of course, there is
threading in twisted, but once the servlet has run and has made a big
honkin' string (http data) it would be nice to cough that down to the
client asynchronously. This would have implications for response.flush()
3. Am I crazy? Maybe.