Depending on how you design things, nsv isn't really the best choice, since growth is unbounded. You're probably better off using the new ns_cache Tcl API, which allows you to create size or time based caches. Look for that as part of the upcoming AOLserver 4.5 release, which we'll hopefully be tagging "officially" in the next couple of weeks. Until then, you can just check out the AOLserver head if interested.

$TOP/aolserver/nsd/cache.c

One other suggestion would be to keep the APIs flexible enough to support different types of data stores (disk, DB, nsv, cache, etc.). One way to do this would be to provide an API that would allow the user to register read and write callbacks.

- n


On Sep 23, 2005, at 2:35 PM, Bas Scheffers wrote:

I just looked at the code. It is completely tied into using the database as persistant storage (and caches using nsv), which of course is not acceptable if we want it out of the box in AOLserver.


-- AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.

Reply via email to