On Apr 10, 2006, at 4:01 PM, David K. Hess wrote:

> How about a combination of both approaches? I would create
> TwistedSite which is a subclass of Site. TwistedSite would have a
> standalone() method that defaults to returning True which results
> in a reactor.run() call when start_web is invoked and results in
> overall "QP is the application" behavior. Combined with the
> __class__ hook you suggest above, this makes the general twisted
> case manageable from bin/qp and very simple for users to accomplish.

I think run_web() should just do what the name implies.
Having an additional not-really switch doesn't seem
clearer to me.

I think we have a way to handle the general case, and a
way to handle your unusual case, so it seems like we should
be happy.