Re: [Zope-dev] Storing references in objects accross requests - bad or OK?

2004-06-14 Thread Dario Lopez-Kästen
Dieter Maurer wrote: Urgent recommendation: avoid storing acquisition wrapped objects across requests, store paths instead and locate the objects by means of the paths. Thank you Dieter and others that have helped me. It seems the best way is either to rethink the way I am doing things, or to

[Zope-dev] Storing references in objects accross requests - bad or OK?

2004-06-13 Thread Dario Lopez-Kästen
hello, I am am worrying a problem here, where I need to store references to objects in my own objects, while at the same time needing to store and retreive my objects later. Here is an example of what I need to do: in a product BooTool for Zope I have: class Foo: def __init__(self, data,

Re: [Zope-dev] Storing references in objects accross requests - bad or OK?

2004-06-13 Thread Dieter Maurer
Dario Lopez-Kästen wrote at 2004-6-13 12:43 +0200: I am am worrying a problem here, where I need to store references to objects in my own objects, while at the same time needing to store and retreive my objects later. Your problem can be summarized by storing acquisition wrappers (of persistent