The current version of ns_cache is not virtual server aware, in other words all virtual servers share one global cache space and one thread-local cache per thread even when they're shared by several virtual servers.
This makes it impossible to set up multiple OpenACS sites using the new virtual serving feature, as we use ns_cache heavily. We could hack OpenACS to generate cache names guaranteed to be unique but making ns_cache virtual server aware is the right solution.
I sat down Friday afternoon with Jim's excellent short document describing how to make a module virtual server aware, and after an hour or two ended up with a modified ns_cache that fits the bill. The necessary changes were simple. I've tested it using multiple instances of OpenACS and it seems to work fine.
So ... my questions are simple. Who maintains ns_cache these days? Who has commit rights to CVS? How do I get these modifications accepted? Should the maintainer (Rob?) review my changes?
-- Don Baccus Portland, OR http://donb.photo.net, http://birdnotes.net, http://openacs.org
I. To remove yourself from this list:
Send a message to "[EMAIL PROTECTED]" with the following text in the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/
