[Zope] How good is Zope at handling concurrent read/write requests..

Chris McDonough chrism@digicool.com
Thu, 14 Jun 2001 20:26:57 -0400


Tommy Johnson wrote:
> 
> >The only problem you may have is if lots of users write to the property at
> the same time.  Then
> > you might get a ConflictError.  See:
> >
> > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/zope-devel/DevGuide
> > /Persistence.stx?rev=1.21&content-type=text/vnd.viewcvs-markup
> >
> > for more information on conflicts.  It won't be a problem as long as you
> > don't hammer the property with writes.
> >
> > -Michel
> 
> So, basicly it doesn't handle concurrency. 

No, it does handle concurrency via an optimistic concurrency control
strategy.

> Yes, multiple users can "view",
> but isn't that what a web server is supposed to do? The real issue of

Multiple users can write too.  The point is that performance begins to
degrade when lots of writes are happening at the same time.

> "concurrency" is whether it handles multiple users trying to write to a
> property at the same time. Obviously, the answer is no.

This is incorrect.

> 
> It would be nice if I could find some way to "Lock" a transaction, similiar
> to ColdFusion's <CFLock> tag.

There's no need.  Just let the application server handle it.