Instantiating Multiple Browser ID Managers
I've got a situation where different sites (within the same Zope 2.6.2 install) have different sessioning needs, and I'd like to be able to set up different browser_id_manager objects to handle the different cases. The 2.6 Zope Book suggests doing this by deleting the root browser_id_manager and instantiating new versions in the most deeply nested containers. Makes sense -- except that I'm unable (with role manager) to delete the root browser_id_manager. (I tried deleting the root session_data_manager first. That worked. But I still wasn't able to delete the root browser_id_manager). Any body got any clues I might follow on this one? Thanks! -- ______________________________________________________ Steve McMahon Reid-McMahon, LLC
Steve McMahon wrote:
Any body got any clues I might follow on this one?
You'll have to alter OFS/Application.py if you need to delete the root browser id manager. A lot of that infrastucture (sessioning) has been installed and then locked down so that users can't remove it. I assume this is because its fragile and relies on a lot of external products configured "just so" in order to work right. -- Jamie Heilman http://audible.transient.net/~jamie/ "Paranoia is a disease unto itself, and may I add, the person standing next to you may not be who they appear to be, so take precaution." -Sathington Willoughby
participants (2)
-
Jamie Heilman -
Steve McMahon