p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed a long line, a typo, and a few misspellings from [9727]. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@9729 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Gary Wilson Jr 2009-01-11 05:47:06 +00:00
parent c01098e9cb
commit 11d382c6c4
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/topics/http/sessions.txt
View File

@ -57,29 +57,29 @@ sure you've configured your cache; see the :ref:`cache documentation
.. warning:: .. warning::
You should only use cache-based sessions if you're using the Memcached cache You should only use cache-based sessions if you're using the Memcached
backend. The local-memory cache backend doesn't retain data long enough to cache backend. The local-memory cache backend doesn't retain data long
be a good choice, and it'll be faster to use file or database sessions enough to be a good choice, and it'll be faster to use file or database
directly instead of sending everything through the file or database cache sessions directly instead of sending everything through the file or
backends. database cache backends.
Once your cache in configured, you've got two choices for how to store data in Once your cache is configured, you've got two choices for how to store data in
the cache: the cache:
* Set :setting:`SESSION_ENGINE` to * Set :setting:`SESSION_ENGINE` to
``"django.contrib.sessions.backends.cache"`` for a simple caching session ``"django.contrib.sessions.backends.cache"`` for a simple caching session
store. Session data will be stored directly your cache. However, session store. Session data will be stored directly your cache. However, session
data may not be persistant: cached data can be evicted if the cache fills data may not be persistent: cached data can be evicted if the cache fills
up or if the cache server is restarted. up or if the cache server is restarted.
* For persistant, cached data, set :setting:`SESSION_ENGINE` to * For persistent, cached data, set :setting:`SESSION_ENGINE` to
``"django.contrib.sessions.backends.cached_db"``. This uses a ``"django.contrib.sessions.backends.cached_db"``. This uses a
write-through cache -- every write to the cache will also be written to write-through cache -- every write to the cache will also be written to
the database. Session reads only use the database if the data is not the database. Session reads only use the database if the data is not
already in the cache. already in the cache.
Both session stores are quite fast, but the simple cache is faster because it Both session stores are quite fast, but the simple cache is faster because it
disreguards persistance. In most cases, the ``cached_db`` backend will be fast disregards persistence. In most cases, the ``cached_db`` backend will be fast
enough, but if you need that last bit of performance, and are willing to let enough, but if you need that last bit of performance, and are willing to let
session data be expunged from time to time, the ``cache`` backend is for you. session data be expunged from time to time, the ``cache`` backend is for you.