RE: [Zope-dev] New Counter Product
Michel wrote:
Howard wrote:
1. How can I create a variable within a Product that will not be persistent (i.e. will not be written to disk)?
Prefix your variable name with _v_. If you don't want the attribute foo to be persistent, call it _v_foo.
But alas, there's a dark side to this. If you're object gets swapped out by the Zope cache manager, splat, there goes the updates since your last change. Presumably it wouldn't be as it would be getting used a lot. There is a way to make your objects "sticky", i.e. they won't be deactivated. But Jim isn't comfortable documenting it. Sticky appears to be the operative term here... --Paul
On Wed, 24 Mar 1999, Paul Everitt wrote:
There is a way to make your objects "sticky", i.e. they won't be deactivated. But Jim isn't comfortable documenting it.
Sticky appears to be the operative term here...
--Paul
How about adding notification before an object is about to swapped out? That would be the time to store this value away permanently... ------- Jordan B. Baker -- jbb@spyderlab.com weaving the web @ http://www.spyderlab.com
At 06:16 25/03/99 , Jordan B. Baker wrote:
On Wed, 24 Mar 1999, Paul Everitt wrote:
There is a way to make your objects "sticky", i.e. they won't be deactivated. But Jim isn't comfortable documenting it.
Sticky appears to be the operative term here...
--Paul
How about adding notification before an object is about to swapped out? That would be the time to store this value away permanently...
That would be something for a new Event structure in Zope. I think there are already too many different notification calls... A Event handling mixin would be nice... you know, registering which Events are available on a given object, registering of event listeners, standards towards canceling events.... Are there any ideas/plans on this DC? -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-6254545 Fax: +31-35-6254555 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------
On Thu, 25 Mar 1999, Jordan B. Baker wrote:
On Wed, 24 Mar 1999, Paul Everitt wrote:
There is a way to make your objects "sticky", i.e. they won't be deactivated. But Jim isn't comfortable documenting it.
Sticky appears to be the operative term here...
--Paul
How about adding notification before an object is about to swapped out? That would be the time to store this value away permanently...
<day dream> Oh to have a few event hooks.... like object about to be removed, system about to be shut down, object about to be added. Oh the possabilities. </day dream>
participants (4)
-
Jordan B. Baker -
Martijn Pieters -
Paul Everitt -
Scott Robertson