Nothing particularly, but there's a better way to do it:
There are multiple ways to do it but it does not mean that server should allow only one way for developer. This is the reason why projects fork, if it is not flexible enough and not willing to be extended enough.
>
Look at the aolserver head, at nsd/limits.c. A 'limits' is a collection of setting such as max upload size, timeout etc. You create one or more of these then bind them to a URL, just like ns_register_proc.
May be limits is a good idea for Url based requests but for server side applications how i am supposed to use ns_cache with different timeout settings, Do not tell me emulate this via url procs. Cache is generic API which should not be bound to URL processing at all. AOLserver does it but it looks like the aolserver server is dedicated for URL processing only, as webserver only, that was the reason of forking to make naviserver more generic and feature-full. I will not agree to follow Aolserver path.
PS: Also, if you are not be at the computer for along time do not commit big patches or big changes, now everybody is waiting for you even to discuss things and we are all stuck.
-- Vlad Seryakov 571 262-8608 office [EMAIL PROTECTED] http://www.crystalballinc.com/vlad/
