Hi, I would like to know the best way to ensure all _v_ attributes of a particular object get cleared in all Zope instances. My configuration is : several Zope instances <-> Zeo I was thinking about changing a non volatile attribute on the object : this should cause it to be reloaded in all connections of all Zope instances, isn't it ? (I know the downside : storing a new version of the object in the ZODB, but it does not matter to me on this particular case). It did that, but it does not appear to work... It seems that on the Zope instance I do it it's fine, but not on the others. Pascal ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************
Pascal Peregrina wrote at 2005-2-15 14:17 +0100:
I would like to know the best way to ensure all _v_ attributes of a particular object get cleared in all Zope instances. My configuration is : several Zope instances <-> Zeo
I was thinking about changing a non volatile attribute on the object : this should cause it to be reloaded in all connections of all Zope instances, isn't it ?
Yes, but with the exception of the modifying connection. There, you would need to clear the "_v_" attributes explicitely.
... It did that, but it does not appear to work... It seems that on the Zope instance I do it it's fine, but not on the others.
That is almost unbelievable... How to you check in the other instance? You know that invalidations are only processed at new requests? -- Dieter
participants (2)
-
Dieter Maurer -
Pascal Peregrina