Chris Withers wrote: Shame though, since storing objects in the session so different frames can get hold of them without lots of computation seemed like a realyl ncie idea :-S Maybe you can use a RAM cache manager for this? It doesn't store stuff in ZODB. the main storage in the session.
How does this relate to sessioning? - Original Message - From: Chris Withers [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, January 09, 2002 6:09 AM Subject: [Zope-dev] Zope 2.5.0b3 a UnpickleableError Hi, trying to use the new sessioning in Zope 2.5.0b3 and get this:
Chris McDonough wrote: How does this relate to sessioning? Well, I was trying to store a DirectoryView object in the session so I could get to it easily from a multiple-frame page. Of course, this means the DriectoryView gets committed to a storage. Now DirectoryViews have FSPythonScripts as
Now DirectoryViews have FSPythonScripts as attributes, so I'm guessing that when the DirectoryView gets committed to the TemporaryStorage, the FSPythonScripts do as well. ...and apparently they don't like being pickled :-( Ah I see. What's probably happening here is that FSPythonScripts