#12487: authenticated user alwayse fetch from database for each request
-------------------------------------+--------------------------------------
Reporter: anonymous | Owner: nobody
Status: closed | Milestone:
Component: Authentication | Version: 1.1
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
An interesting idea, but I don't think it's as simple as you make out.
There are all sorts of cache invalidation issues hiding underneath this.
I am also highly skeptical that reloading the user, groups and permissions
is a bottleneck in your application. I don't doubt that this *could* be
optimized, but I find it hard to believe that this is the biggest
performance improvement available to your (or any) project.
Marking wontfix for now, but willing to entertain discussion if someone is
particularly enthused by the idea.
--
Ticket URL: <http://code.djangoproject.com/ticket/12487#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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/django-updates?hl=en.
