> > 1.0), so I try to use request_started.
>
> I think you're running into conceptual problems with both the
> "request_started" signal, and the architecture of Django itself.
>
> The "request_started" signal simply means "an HTTP request has come
nal to get into
> 1.0), so I try to use request_started.
I think you're running into conceptual problems with both the
"request_started" signal, and the architecture of Django itself.
The "request_started" signal simply means "an HTTP request has come
in, and proce
Is seems that request_started & request_finished are used by the db to
manage connections, so I would expect it to work as defined.
I have some code for processing the urlsconf so signals seems like the
obvious tool. Apparently there is on server_started signal firing when
configuration is comple
