On Mon, 2003-12-15 at 07:34, Dieter Maurer wrote:
I don't think it makes a lot of sense to put an __del__ method on a
Persistent object.
I just read in cPersistence.c:ghostify:
/* We remove the reference to the just ghosted object that the ring
* holds. Note that the dictionary
On Sun, 2003-12-14 at 16:53, Chris McDonough wrote:
We still use ZODB 3.1 and at least there, the cache verification
protocol seems quite stupid. We will soon switch to ZODB 3.2
and when cache validation still needs minutes, I will need
to look into this...
Apparently, the ZEO in 2.7
On Fri, 2003-12-12 at 23:43, Stuart Bishop wrote:
I've just clarified the issue in the collector. We have since found that
manual product refresh is working, and it is just the automatic product
refresh that gives this error.
I don't mean to sound glib (really), but refresh has always caused
On Sat, 2003-12-13 at 22:10, Stuart Bishop wrote:
Firstly, I've *never* had problems with refresh (as a user of) until
Zope 2.7 (I only use it on my own products, so I must naturally code
in a refresh friendly manner). I'm used to developing with autorefresh
switched on for my products and it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/12/2003, at 5:50 AM, Dieter Maurer wrote:
Stuart Bishop wrote at 2003-12-10 11:24 +1100:
On 08/12/2003, at 12:15 AM, Dieter Maurer wrote:
Playing with Zope Head (as of 2003-12-04) revealed problems with
refresh.
This is not just a 2.8 issue -
Stuart Bishop wrote at 2003-12-10 11:24 +1100:
On 08/12/2003, at 12:15 AM, Dieter Maurer wrote:
Playing with Zope Head (as of 2003-12-04) revealed problems with
refresh.
This is not just a 2.8 issue - the behavior is in the 2.7 betas (at
least
up to beta 2 - havn't tested autorefresh with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/12/2003, at 12:15 AM, Dieter Maurer wrote:
Playing with Zope Head (as of 2003-12-04) revealed problems with
refresh.
This is not just a 2.8 issue - the behavior is in the 2.7 betas (at
least
up to beta 2 - havn't tested autorefresh with beta 3
Jeremy Hylton wrote at 2003-12-7 23:01 -0500:
On Sun, 2003-12-07 at 08:15, Dieter Maurer wrote:
ATT: replacing the cache without clearing it can lead to huge
memory leaks (everything in the old cache is leaked!).
Without commenting on the rest of the bug report, I should mention that
caches
On Mon, 2003-12-08 at 13:17, Dieter Maurer wrote:
Jeremy Hylton wrote at 2003-12-7 23:01 -0500:
On Sun, 2003-12-07 at 08:15, Dieter Maurer wrote:
ATT: replacing the cache without clearing it can lead to huge
memory leaks (everything in the old cache is leaked!).
Without commenting on
On Sun, 2003-12-07 at 08:15, Dieter Maurer wrote:
ATT: replacing the cache without clearing it can lead to huge
memory leaks (everything in the old cache is leaked!).
Without commenting on the rest of the bug report, I should mention that
caches and persistent objects all participate in
10 matches
Mail list logo
