# HG changeset patch
# User Sylvain Thénault <sylvain.thenault@logilab.fr>
# Date 1245154518 -7200
# Node ID 58489d11321577fd23821effa2852b9015a567b3
# Parent  5e142c7a45317e087441a2c05d29e37ea49b5479# Parent  df86450ca65d5e4adb52c9e56da1da813ee6c0fd
merge

diff -r 5e142c7a4531 -r 58489d113215 doc/book/en/development/devrepo/sessions.rst
--- a/doc/book/en/development/devrepo/sessions.rst	Tue Jun 16 14:14:58 2009 +0200
+++ b/doc/book/en/development/devrepo/sessions.rst	Tue Jun 16 14:15:18 2009 +0200
@@ -3,7 +3,24 @@
 Sessions
 ========
 
+There are three kinds of sessions.
+
+* user sessions are the most common: they are related to users and
+  carry security checks coming with user credentials
+
+* super sessions are children of ordinary user sessions and allow to
+  bypass security checks (they are created by calling unsafe_execute
+  on a user session); this is often convenient in hooks which may
+  touch data that is not directly updatable by users
+
+* internal sessions have all the powers; they are also used in only a
+  few situations where you don't already have an adequate session at
+  hand, like: user authentication, data synchronisation in
+  multi-source contexts
+
+Do not confuse the session type with their connection mode, for
+instance : 'in memory' or 'pyro'.
+
 [WRITE ME]
 
 * authentication and management of sessions
-