On 23 Sep 2005, at 19:53, Nathan Folkman wrote:
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
I don't like using nsv for it either (mostly because I am lazy and
can't be bothered writing my own sweeping routine) but not for the
unbounded growth. I guess someone could do a DOS attack by creating
millions of session, but if you are serious about preventing that
kind of attack, you'd use some smart firewall already that will catch
this case. And if you bound the growth, you'll bring the service down
anyway as no legitimite users can create new sessions either.
we'll hopefully be tagging "officially" in the next couple of
weeks. Until then, you can just check out the AOLserver head if
interested.
A good ns_cache API is good, but I still prefer implementing this in
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.
I don't think you even need that, just load the implementation - and
only the implementation - you want, no need for callbacks.
Bas.
--
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.
