On 18/12/2012, at 2:15 PM, Leonardo Rochael Almeida
wrote:
> Hi,
>
> On Mon, Dec 17, 2012 at 10:03 PM, Dylan Jay wrote:
>>
>> On 14/12/2012, at 8:32 AM, Jim Fulton wrote:
>>
>>> On Thu, Dec 13, 2012 at 4:18 PM, Dylan Jay wrote:
>>> ...
I'd never considered that the cache was attached
Hi,
On Mon, Dec 17, 2012 at 10:03 PM, Dylan Jay wrote:
>
> On 14/12/2012, at 8:32 AM, Jim Fulton wrote:
>
>> On Thu, Dec 13, 2012 at 4:18 PM, Dylan Jay wrote:
>> ...
>>> I'd never considered that the cache was attached to the db connection rather
>>> than the thread. I just reread
>>> http://do
On 14/12/2012, at 8:32 AM, Jim Fulton wrote:
> On Thu, Dec 13, 2012 at 4:18 PM, Dylan Jay 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
>> ex
On Thu, Dec 13, 2012 at 4:18 PM, Dylan Jay 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 tune db connect
On 13/12/2012, at 11:07 PM, Jim Fulton wrote:
On Wed, Dec 12, 2012 at 6:31 PM, Dylan Jay 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 api
On Thu, Dec 13, 2012 at 12:11 PM, Leonardo Rochael Almeida
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.
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 he
On Wed, Dec 12, 2012 at 6:31 PM, Dylan Jay 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 a zope thre
On 13 December 2012 00:31, Dylan Jay wrote:
> What if two or more threads could share a zodb cache up until the point at
> which one wants to write. This is the point at which you can't share a cache
> in a consistent manner in my understanding. At that point the transaction
> could be blocked
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 a zope thread
isn't doing any other processing and because there is a 1 th
10 matches
Mail list logo