On Wednesday, July 20, 2011 10:56:18 AM UTC-4, ariel.glez.m wrote: > > what thing replace in web2py the context process
I'm not too familiar with Django and its context processors -- it looks like they automatically add particular variables/objects to your template context before rendering. Note, in web2py, all of the web2py API global objects, including request, response, and session, are automatically available in the environment in which templates are rendered. Also, any variables/objects defined in any model file are available in the template environment. Looking at Django's default context processors, I think most of that stuff is already available in web2py's template environment (e.g., the entire auth object, which is defined in a model file, is available in the template environment, including auth.user). > and midelware of > django.....???? Here's what the book has to say about middleware: http://web2py.com/book/default/chapter/04#WSGI Massimo also suggested some alternatives here: https://groups.google.com/d/msg/web2py/xEwZJeZGhSM/1tdX__F--voJ I think much of what is handled by standard Django middleware is handled (usually automatically and by default) by other means in web2py (e.g., sessions, auth, CSRF protection, transactions, internationalization, etc.). Anthony
