Personally I like the CP filters. I come from a lot of mod_perl
experience. I still develop in it a lot. What I REALLY like about it,
is that I get hooks into the entire Apache server and request cycles.
CherryPy filters are very similar to the apache request cycle (though
the apache request cycle has waaay more hooks).
>From everything I've heard about middleware, it should be possible --
but I've yet to see it in practice.
A lot of what I've been doing with TG is situated on cherrypy
internals. in fact quite a bit of tg itself seems situated on cherrypy
internals.
So for the sake of mye being able to be forward compatible I'll ask
this:
using middleware, how can I do the following:
a- store a per-request variable
b- run code during certain segments of the request
if there's going to be a change away from cherrypy, perhaps there
should be a per-request namespace/object in the next release of tg?
ie, have a tg.current_request wrap cherrypy.request, so that anyone who
is using that bit of cherrypy to manage per-request info will be
compatible
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
