[Zope] [Further investigations] Re: A question about __setstate__ in Shared/DC/ZRDB/Connection.py

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marco Bizzarri wrote:

> Thanks for the suggestion, Tres, I'm trying it right now.

> I think this could be responsible for the problem I had a few months
> ago, under the name: "Asking advice on a Zope "stuck" (or: what did I
> do wrong?)"

> Do you think there will be some sort of "general" solution to the
> problem? I mean, the problem is actually that there are some objects
> which should not be ghostified, or am I wrong?

There are two problems here:

 - Some objects need to be able to mark themselves as "sticky" for
   at least the duration of a transaction;  my workaround is hackish,
   because if you omit the 'del conn._p_changed' it causes the object
   to be written needlessly;  likewise, if the conn object *is* actually
   written to during the transaction, those changes will be discarded.

 - We need a way to keep the Pdata objects from evicting "precious"
   objects;  ideally, Pdata instances would never be added to the cache
   at all.  I worked a bit on a spike in which the Pdata iterator part
   would use a one-off connection with a zero-sized cache, but got
   stuck somewhere;  maybe somebody else can make it work.

Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI07Po+gerLs4ltQ4RAvz1AJ9kZ+XFucS9Eq4rFkGQ7NI12F9ItACeLE9/
YkOPDbgH5UbO+uHQ4IDIyHU=
=y5iN
-----END PGP SIGNATURE-----