[Modeling-cvs] ProjectModeling/Modeling/doc/UserGuide FrameworkTypicalUsage.tex,1.3,1.4

[<sbi...@us...>]

Update of /cvsroot/modeling/ProjectModeling/Modeling/doc/UserGuide
In directory sc8-pr-cvs1:/tmp/cvs-serv7546

Modified Files:
	FrameworkTypicalUsage.tex 
Log Message:
Wrote: details of the integration within zope and sessioning machineries in general.
Note for Mario: this is the first finalized draft of this chapter :)


Index: FrameworkTypicalUsage.tex
===================================================================
RCS file: /cvsroot/modeling/ProjectModeling/Modeling/doc/UserGuide/FrameworkTypicalUsage.tex,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** FrameworkTypicalUsage.tex	10 Mar 2003 21:42:04 -0000	1.3
--- FrameworkTypicalUsage.tex	13 Mar 2003 18:01:30 -0000	1.4
***************
*** 75,79 ****
  
  %%
! \section{Application servers, Zope\label{framework-integration-applications-servers}}
  
  For an application run by an application server, different approaches are
--- 75,79 ----
  
  %%
! \section{Integration within application servers: using the sessioning mechanism\label{framework-integration-application-servers}}
  
  For an application run by an application server, different approaches are
***************
*** 190,200 ****
  
  
  \section{Zope\label{framework-integration-zope}}
  
! \module{ZEditingContextSessioning}
  
  \section{Others\label{framework-integration-others}}
  
! - sessioning 
  
! - cgi? --> do not think so (initialization process is probably too heavy)
--- 190,234 ----
  
  
+ %%
  \section{Zope\label{framework-integration-zope}}
  
! The framework is shipped with a particular component,
! \module{ZEditingContextSessioning}, that makes it possible to have an
! \class{EditingContext} lazily created on a per-session basis.
! 
! When installed in the \code{Products/} folder of a Zope instance, it
! automatically modifies the class \class{TransientObject}\footnote{The
! \code{SESSION} object is an instance of \class{TransientObject}} and adds a
! new method to it: \method{defaultEditingContext}. It also binds itself to the
! sessioning machinery so that the \class{EditingContext} attached to a session
! is automatically finalized when the session is expired.
! 
! 
! Accessing the \class{EditingContext} bound to a particular session is as
! simple as calling \method{defaultEditingContext()} on the \code{SESSION}
! object.
! 
! 
! \begin{notice}
! Zope does not immediately destroy expired sessions ; they are marked as
! expired and are only destroyed when a given thread is elected for doing the
! ''housekeeping'' (see \file{lib/python/Products/Transience/Transience.py},
! method{_getCurrentBucket()}). This means that the
! \method{defaultEditingContext} assigned to a session will not be finalized
! when the session expires, but a certain amount of time afterwards.
! \end{notice}
! 
! 
! 
  
+ %%
  \section{Others\label{framework-integration-others}}
  
! As far as I know the framework has not been integrated in other
! frameworks. However it is shipped with a component,
! \class{utilities.EditingContextSessioning}, which should make it easy to bind
! it to any existing sessioning machinery. The documentation in this module
! gives all necessary details and instructions of use.
  
! We will be happy to hear from you if you integrate it to other development
! platforms!