summaryrefslogtreecommitdiff
path: root/docs/narr/introduction.rst
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2013-10-14 11:23:24 +0200
committerChris McDonough <chrism@plope.com>2013-10-14 11:23:24 +0200
commita87c1972615f98e99b06f9ea335a12104f67e6e0 (patch)
tree4b9f81e2ccf3a3590e539808b72ca443778b3359 /docs/narr/introduction.rst
parent4223668ee4c0d0ac0e981f3241d56ffa805ba6d1 (diff)
parent55917fe91b4344008da352e262dc2135629405d6 (diff)
downloadpyramid-a87c1972615f98e99b06f9ea335a12104f67e6e0.tar.gz
pyramid-a87c1972615f98e99b06f9ea335a12104f67e6e0.tar.bz2
pyramid-a87c1972615f98e99b06f9ea335a12104f67e6e0.zip
Merge branch 'master' of github.com:Pylons/pyramid
Diffstat (limited to 'docs/narr/introduction.rst')
-rw-r--r--docs/narr/introduction.rst17
1 files changed, 8 insertions, 9 deletions
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst
index ece720a97..a9c5fdfbd 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -180,10 +180,9 @@ Fully Interactive Development
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When developing a Pyramid application, several interactive features are
-available. Pyramid can automatically utilize changed templates when rendering
+available. Pyramid can automatically utilize changed templates when rendering
pages and automatically restart the application to incorporate changed python
-code. Plain old ``printf()`` calls used for debugging can display to a
-console.
+code. Plain old ``print()`` calls used for debugging can display to a console.
Pyramid's debug toolbar comes activated when you use a Pyramid scaffold to
render a project. This toolbar overlays your application in the browser, and
@@ -418,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`.