it's last:
I don't know how to provide order of processing outside middlewares...
i stopped on this:
settings.py:
MIDDLEWARE_CLASSES = (
'django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
megathanks to all
I will try to use something like:
(r'^members/', include('members.urls'), {'auth':True})
but {'auth':True} will consist of name of handler (handlers)
I'll try to create 1 middleware to process this filters. All handlers
will be called according by its names.
Yes, this is a
The request processing can be easy if developers of sites can define
prehandlers and posthandlers for each urls.py (or views.py?).
prehandler: the connection middleware. It calls before request
object was created. Only connection detailes needed for prehandler
processing (no session, no
On Nov 9, 3:21 pm, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> +1. Keeping all translations in one table instead of creating separate
> tables for each user table is what I was going to propose but you beat
> me :-)
This has one potential benefit - ease global search implementa
Forgive me for silly question, but why 'short_description' used in
contrib.admin, instead of '__doc__' attribute?
--
serg.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" grou
