On Wed, Dec 12, 2012 at 6:31 PM, Dylan Jay d...@pretaweb.com wrote:
Hi,
I've been working with zope for over 12 years and something that
keeps coming up is sacling IO bound operations in Zope. The typical
example is where you build an app that calls external apis. While
this is happening
Hi
In ERP5, the rule is that you should never talk to external systems as
a synchronous response to a user request, and you should avoid, at all
costs, writing to ZODB at the same time as talking to external systems
(or the external system must be able to handle this gracefully).
Of course, it
On Thu, Dec 13, 2012 at 12:11 PM, Leonardo Rochael Almeida
leoroch...@gmail.com wrote:
(or the external system must be able to handle this gracefully).
By this I meant conflict errors, for example SMTP servers posting
INTO Zope can retry sending later in case of error.
On 13/12/2012, at 11:07 PM, Jim Fulton j...@zope.com wrote:
On Wed, Dec 12, 2012 at 6:31 PM, Dylan Jay d...@pretaweb.com wrote:
Hi,
I've been working with zope for over 12 years and something that
keeps coming up is sacling IO bound operations in Zope. The typical
example is where you build
On Thu, Dec 13, 2012 at 4:18 PM, Dylan Jay d...@pretaweb.com wrote:
...
I'd never considered that the cache was attached to the db connection rather
than the thread. I just reread
http://docs.zope.org/zope2/zope2book/MaintainingZope.html and it says
exactly that.
So what your saying is I'd
We've recently noticed some fairly significant speed issues cropping up on a
customer site (zope 3 / bluebream-ish stack). We use zc.catalog and its Value
and Set indexes and it's serves us rather well, up until recently.
In a *cold start* in one environment, profiling the home page reported 27
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have gotten the trunk of persistent to build an test persistent's
extension modules under Python 3.2. There is a segfault under Python 3.3
which looks to be an actual Python bug:
http://bugs.python.org/issue16676
I will make a 4.0.5 release once
