On Sunday 16 March 2003 10:07, you wrote:
> > I would probably take the approach of adding a new command to ns_cache,
> > using servPtr == NULL as a flag seems a bit of a kludge. Most of the
> > code works on a cache pointer with no other context information,
>
Don,
Instead of adding new cmd, I changed the API (backward-compatible)
to read:
ns_cache create name
?-size size? ?-timeout timeout? ?-thread boolean | -common boolean?
So, now we have per-thread, per-virtual-server and common caches.
The per-virtual-server is the most commonly used type, therefore it needs
no extra options.
Others are less important, thus need extra option (-thread or -common)
Note that -thread and -common are mutualy exclusive.
The name of the new option "-common" is the best what came to my
mind. If somebody has a better idea, please step out.
Cache name resolving is done by first looking into the
per-virtual-server caches and if none found, into common caches.
I will commit this into SF tomorrow, after checking it with Purify
just to be sure. I'll tag it with the 1.5 version since it should also
be usable (albeit not necessary) for 3.x servers.
Cheers,
Zoran
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list: http://www.aolserver.com/listserv.html
List information and options: http://listserv.aol.com/