summaryrefslogtreecommitdiff
path: root/docs/narr
diff options
context:
space:
mode:
authorSteve Piercy <web@stevepiercy.com>2013-10-08 16:51:24 -0700
committerSteve Piercy <web@stevepiercy.com>2013-10-08 16:51:24 -0700
commit7f7d86e1e767f0339266d00c3a4723477add28b5 (patch)
treed474b33ec2320f5849d35d54e5e96c2b00daeced /docs/narr
parent6b2e8ee2a63f601a1708c0e74e6ea5b3551507f1 (diff)
parentd7f8766ef2154c64b9fc040e5bf0a8249e5c366f (diff)
downloadpyramid-7f7d86e1e767f0339266d00c3a4723477add28b5.tar.gz
pyramid-7f7d86e1e767f0339266d00c3a4723477add28b5.tar.bz2
pyramid-7f7d86e1e767f0339266d00c3a4723477add28b5.zip
Merge branch 'origin/master'
Diffstat (limited to 'docs/narr')
-rw-r--r--docs/narr/introduction.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst
index bb2d85e94..a9c5fdfbd 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -417,12 +417,12 @@ Sessions
Pyramid has built-in HTTP sessioning. This allows you to associate data with
otherwise anonymous users between requests. Lots of systems do this. But
-Pyramid also allows you to plug in your own sessioning system by creating
-some code that adheres to a documented interface. Currently there is a
-binding package for the third-party Beaker sessioning system that does exactly
-this. But if you have a specialized need (perhaps you want to store your
-session data in MongoDB), you can. You can even switch between
-implementations without changing your application code.
+Pyramid also allows you to plug in your own sessioning system by creating some
+code that adheres to a documented interface. Currently there is a binding
+package for the third-party Redis sessioning system that does exactly this.
+But if you have a specialized need (perhaps you want to store your session data
+in MongoDB), you can. You can even switch between implementations without
+changing your application code.
Example: :ref:`sessions_chapter`.