Update of /cvsroot/modeling/ProjectModeling/Modeling/doc/UserGuide
In directory sc8-pr-cvs1:/tmp/cvs-serv24615/UserGuide
Modified Files:
FrameworkTypicalUsage.tex
Log Message:
Wrote subsection "Sessioning" in section "Application servers"
Index: FrameworkTypicalUsage.tex
===================================================================
RCS file: /cvsroot/modeling/ProjectModeling/Modeling/doc/UserGuide/FrameworkTypicalUsage.tex,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** FrameworkTypicalUsage.tex 10 Mar 2003 19:12:11 -0000 1.2
--- FrameworkTypicalUsage.tex 10 Mar 2003 21:42:04 -0000 1.3
***************
*** 13,16 ****
--- 13,19 ----
take different approaches. We'll see how this can be done, either in a
pure-python application or within application servers like Zope or others.
+ We suggest that you read the whole chapter, whatever your specific needs are:
+ it contains important informations explaining how the framework reacts and how
+ it can be used in standard situations.
%%
***************
*** 133,139 ****
! For these reasons, we do not recommend that way -- except maybe in special
! cases where the database is a small one, but even then, why would you use a
! database if you can't count on your application to scale when the db is
growing?
--- 136,142 ----
! For these reasons, we do not recommend this solution -- except maybe in
! special cases where the database is a small one, but even then, why would you
! use a database if you can't count on your application to scale when the db is
growing?
***************
*** 146,154 ****
contain at most. Then, when the maximum number of objects is reached, it would
be possible to automatically clean the \class{EditingContext} (the oldest
! object would be re-faulted/invalidated, or ''ghostified'' in {\sc zodb}
jargon).
! There is no {\sc eta} for this feature however, it is just a {\sc todo}
! item. If you think you need the feature, please go ahead and let us know!
\end{notice}
--- 149,157 ----
contain at most. Then, when the maximum number of objects is reached, it would
be possible to automatically clean the \class{EditingContext} (the oldest
! object would be re-faulted/invalidated, or ''ghostified'' in ZODB
jargon).
! There is no ETA for this feature however, it is just a TODO item. If you think
! you need the feature, please go ahead and let us know!
\end{notice}
***************
*** 157,169 ****
The second approach involves a per-session creation mechanism for
! \class{EditingContext}s.
\paragraph*{Known problem:}
! Inter-EC notifications of changes is not handled yet
\section{Zope\label{framework-integration-zope}}
! TBD
\section{Others\label{framework-integration-others}}
--- 160,196 ----
The second approach involves a per-session creation mechanism for
! \class{EditingContext}s.
!
!
! The framework provides the module \module{utilities.EditingContextSessioning}
! for such situations. This module acts as central repository to which a
! sessioning mechanism can be bound for creating, accessing and destroying an
! \class{EditingContext} as sessions come up and expire.
! The module documentation gives full details about its methods and how they can
! be used.
\paragraph*{Known problem:}
! By definition, such a configuration isolates the changes different users make
! {\em until} they are committed. The problem here is that even {\em after} a
! user has committed changes, the other users that are already connected and
! whose session already got an \class{EditingContext} {\bf will not see} the
! changes made to objects previously fetched -- new users connecting afterwards
! will see the changes, though, as will current users who did not fetch the
! updated objects before they were committed.
!
! \begin{quote}
! This is due to a feature missing in the framework, where changes to an
! EditingContext are not broadcasted to others. This is a TODO, highly
! prioritary, which is planned to be solved in the release after 0.9 (ETA: end
! of march 2003).
! \end{quote}
!
! There is currently no satisfying solution for this problem.
!
\section{Zope\label{framework-integration-zope}}
! \module{ZEditingContextSessioning}
\section{Others\label{framework-integration-others}}
|
