FWIW, allowing Zope to unpickle data that it receives remotely is a pretty big security risk. It sounds like you probably know this and it's "OK" in your case, but just wanted to send a message to make sure..
On Wednesday, July 3, 2002, at 05:54 , Terry Hancock wrote:
Hi all,
I'm hoping this is the last mystery before I release ... :-D
For good or ill, I used a variation of the MiniPickle module (see the example on zope.org) to pack python data structures into a cookie. (I had to add an extra hex-encoding part to make legal cookies).
I needed an external python method to do this in the prototype, and I thought it'd be trivial to just attach these as regular python methods in the product.
However, when I try to call my "mini_dumps" method, I get a complaint about not being able to pickle an object in an "acquisition wrapper." A little searching on zope.org suggests this is referring to the internal mechanism that Zope uses to provide acquisition services.
But why wouldn't the external method complain about it? And how can I unwrap this object? (I guess this means getting a direct reference to the object instead of an indirect one, though I'm still foggy on how acquisition works -- it seems pretty magical still).
Thanks, Terry
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"