Michele Cella wrote:
Right now CherryPy is the blocker, and once it is working there I think
that should transfer to TG fairly easily, possibly (hopefully) even
retroactively (e.g., if you are running TG 0.9 with whatever version of
CherryPy where this is working). Right now CherryPy isn't offering a
sufficient WSGI-related API, and I don't know if that's because of
underlying architectural issues, or that the APIs just don't expose what
they should.
Just wondering if you have already seen last Fumanchu's reply to your
questions on ticket #145:
http://www.cherrypy.org/ticket/145
I had not seen that, thanks for noting that. Added myself to CC as
well. As I look through the CherryPy code, maybe it would be possible
to figure this out with a sufficiently magical cherrypy.root object,
though I suspect some serious monkeypatching to cherrypy.config might
also be necessary (to make up for no complete and global set of
configuration), and I might just need to make cherrypy.root a
threadlocal object. That's probably the thing most likely to work.
A positive part of a monkeypatch is that it will be immediately usable
with TG, probably/hopefully without TG needing to know that. Though I
suspect there may be some configuration issues... is TG still using
CherryPy's configuration, or is it starting to handle that on its own?
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
