Any particular reason not to stow the intermediate thing outside of the ZODB - an external method can write a string to disk or a cookie to the client ? Cookie maybe - so you don't need to futz with unique filenames and cleaning up... <199906080956.taa0719-@mbuna.arbhome.com.au> wrote: Original Article: http://www.egroups.com/group/zope/?start=5906
In more detail, the problem I have is that in the bobo_traverse method, if I get a constraint, I want to store this. The way I do this is to instantiate a new DMC - but one that's non-persistant, populate it, then return it. Unfortunately to get it to acquire everything else it needs, I need to attach it to the 'self' object with something like
self.new = DMC_nonP(self.id, self.name, ....) ... set the magic in the new object ... return self.new
Unfortunately this self.new assignment makes an entry in the ZODB. Blah.
Anyway, I plan to fling a release of some sort out tonight, bug or no bug.
Anthony
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )