yes
On Tuesday, 6 August 2013 07:14:34 UTC-5, Anthony wrote: > > > > On Tuesday, August 6, 2013 3:13:48 AM UTC-4, Massimo Di Pierro wrote: >> >> The wsgi middleware is really not the web2py way of doing this. It is a >> compatibility mode of allowing third party middleware of interoperating >> with web2py. It has only been tested in simple cases. It was recently >> rewritten (untested) nobody uses it, and I am considering dropping the >> feature. > > > You're talking only about the internal > middleware<http://web2py.com/books/default/chapter/29/04/the-core?search=_caller#Internal-middleware>feature > (i.e., @request.wsgi.middleware), right? > > Please tell us more what kind of interception you want to do. In my view >> some can be done at the web server level, some at the routes.py level and >> some at the response._caller level. >> > > Good point -- response._caller is another good option, especially if you > need to do something *after* the controller action finishes. > > Anthony > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
