[Zope] conflicts, sessions, and programming best practices guidelines

[Dennis Allison]

Peter, 

That's pretty much what we've done, but it is not really enough in
our case.  Our sites are interactive with lots of per user state.  We make
fairly heavy use of session variables to track the state.  Our number of
simultaneous users is also fairly high.  In addition, during development,
we structured things for ease of development rather than for mimimum
liklihood of conflict errors.  At this point we are seeing many conflicts 
and interactions with both the sessioning mechanism and the persistence
mechanism--or so it appears.

Even when we resolve the current database interaction problem, a 
refactoring seems in order to ensure the number of conflicts is kept to a 
minimum.



On Tue, 15 Nov 2005, Peter Bengtsson wrote:

> I don't know of any documentation but (correct me if I'm wrong) but
>  - install zope 2.8.0 or something higher that uses zodb 3.4
>  - use zeo's and load balancers so that certain requests don't clog your pipes
> 
> On 11/15/05, Dennis Allison <allison at shasta.stanford.edu> wrote:
> >
> > Has anyone prepared a set of best practice guidelines on the techniques to
> > use to minimize conflicts?
> >
> > It is becoming clear that we need to do to refactor some of our code to
> > get us out of our current conflict pickle.
> >
> > A quick google produced lots of commentary but nothing I could hand to our
> > programmers as guidelines.
> >
> >
> >
> > _______________________________________________
> > Zope maillist  -  Zope at zope.org
> > http://mail.zope.org/mailman/listinfo/zope
> > **   No cross posts or HTML encoding!  **
> > (Related lists -
> >  http://mail.zope.org/mailman/listinfo/zope-announce
> >  http://mail.zope.org/mailman/listinfo/zope-dev )
> >
> 
> 
> --
> Peter Bengtsson,
> work www.fry-it.com
> home www.peterbe.com
> hobby www.issuetrackerproduct.com
> 

--