----- Original Message -----
From: "Berthold Stöger" <[EMAIL PROTECTED]>
To: <zope@zope.org>
Cc: "Dieter Maurer" <[EMAIL PROTECTED]>
Sent: Thursday, June 29, 2006 2:35 PM
Subject: Re: [Zope] ConflictError with *one* ZEO client?
On Thursday 29 June 2006 18:56, Dieter Maurer wrote:
Good application design would make the conflict probability so low
that it is very unlikely that a "ConflictError" propagates to
the user.
For more complicated applications this is only possible with locking.
Does
Zope provide locking primitives?
Or, ideally, something like asynchronous message passing? I would love to
be
able to start a transaction and, if it finishes in less than x seconds,
tell
the user the result or, if it hasn't finshed by then, that the transaction
is
being processed, please come back later.
If you are interested in async programming with zope have a look at twisted,
here's some info:
http://twistedmatrix.com/projects/core/documentation/howto/index.html
Jonathan
_______________________________________________
Zope maillist - Zope@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 )
