[Zope] Re: Saving Pipe3 object

[Alexander Staubo]

Good point; it's the exact same reason why the second version of my
Guest Counter product is broken. (Nasty -- I quality-assured the wrong
script before sending it off to production ;-).)

Is there any way to create objects that are persistent during the
lifetime of the Zope process? I just realized that making the "guests"
attribute of the GuestCounter class volatile doesn't really make sense,
because the object isn't guaranteed to be cached, and the attribute
shouldn't be persistent except in memory.

I guess I can store the attribute as part of the product instance, but
that's too dirty, unless it's the only way.

-- 
Alexander Staubo             http://www.mop.no/~alex/
"QED?" said Russell.
"It's Latin," said Morgan. "It means, 'So there you bastard'."
--Robert Rankin, _Nostramadus Ate My Hamster_

> -----Original Message-----
> From: Phillip J. Eby [mailto:pje@telecommunity.com]
> Sent: 27. august 1999 04:34
> To: zope@zope.org
> Subject: RE: [Zope] Re: Saving Pipe3 object
> 
> 
> At 04:30 AM 8/27/99 +0200, Alexander Staubo wrote:
> >The underscore prefix should be enough: Your variable can be named
> >_long_R_Pipe and it won't be pickled.
> >
> >DC uses the _v_ prefix convention for various stuff, possibly meaning
> >"value"... Who knows.
> 
> It stands for 'volatile'.  In other words, the opposite of 
> 'persistent'.
> _v_ attributes are not stored as part of an object's 
> persistent state in
> the database.  It's used for things which should only exist while the
> object is loaded into memory.
> 
> 
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://www.zope.org/mailman/listinfo/zope
> 
> (To receive general Zope announcements, see:
> http://www.zope.org/mailman/listinfo/zope-announce
> 
> For developer-specific issues, zope-dev@zope.org -
> http://www.zope.org/mailman/listinfo/zope-dev )
>