Stores the user's information in the session, reucing database queries by a lot.
Project description
===================
django-session-user
===================
This app is a simple piece of middleware that can be added to your Django
project which will store and retrieve the logged-in user's information from
the session.
Installation
------------
Add the sesionuser middleware line to your MIDDLEWARE_CLASSES after the
AuthenticationMiddleware:
MIDDLEWARE_CLASSES = (
# ...
'django.contrib.auth.middleware.AuthenticationMiddleware',
'sessionuser.middleware.SessionUserMiddleware',
# ...
)
Why do this?
------------
Your server is already fetching the contents of the user's session, which
already contains the user's identity. Why not store the rest of the user
class's data along with it? That way you don't have to make a request to the
database for every authenticated web request.
Additionally if you are using a cookie-based session backend (like
django-cookie-sessions, written by yours truly) you can have other systems,
maybe even non-Django systems, which read the cookie and know more information
about the user.
Customizable Settings
---------------------
COOKIE_USER_REFRESH_TIME [= 14400]:
The number of seconds that need to elapse before the user is fetched from
the database instead of trusting the cookie. This is useful for making
sure that even if the user's properties are changed in the database,
the user's cookie will still be updated.
django-session-user
===================
This app is a simple piece of middleware that can be added to your Django
project which will store and retrieve the logged-in user's information from
the session.
Installation
------------
Add the sesionuser middleware line to your MIDDLEWARE_CLASSES after the
AuthenticationMiddleware:
MIDDLEWARE_CLASSES = (
# ...
'django.contrib.auth.middleware.AuthenticationMiddleware',
'sessionuser.middleware.SessionUserMiddleware',
# ...
)
Why do this?
------------
Your server is already fetching the contents of the user's session, which
already contains the user's identity. Why not store the rest of the user
class's data along with it? That way you don't have to make a request to the
database for every authenticated web request.
Additionally if you are using a cookie-based session backend (like
django-cookie-sessions, written by yours truly) you can have other systems,
maybe even non-Django systems, which read the cookie and know more information
about the user.
Customizable Settings
---------------------
COOKIE_USER_REFRESH_TIME [= 14400]:
The number of seconds that need to elapse before the user is fetched from
the database instead of trusting the cookie. This is useful for making
sure that even if the user's properties are changed in the database,
the user's cookie will still be updated.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file django-session-user-0.1.1.tar.gz
.
File metadata
- Download URL: django-session-user-0.1.1.tar.gz
- Upload date:
- Size: 3.8 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | a80293ba698dcd2305b33fa92fc74de7a84ee8a0e7c978f9ef125da2441ad290 |
|
MD5 | 719e9a73586d1622189bd1857846f841 |
|
BLAKE2b-256 | 55bb9a9b6cae355877ee34be0068a2a859e1b5eabe2acc113939b40f51baebcb |