Re: [naviserver-devel] [naviserver-commits] naviserver ChangeLog, 1.405, 1.406

[Zoran V. <zv...@ar...>]

Am 21.06.2006 um 19:01 schrieb Stephen Deasey:

> 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.

But Stepehn, lets look this from another perspective...

We use NS to about 80-85% as a general purpose application
server and to the rest as webserver. For us, binding a
limit to an URL does not mean much. Instead we have divided
our code in multiple C and Tcl modules we plug into the server
and each module has its own configuration section where we draw
defaults/limits etc, falling back to defaults built into the server.

WFor example, we use -timoeut option for generating cache to be
able to create a cache per-module with per-module defaults.
This is of course different for every module. How are we to solve
this with the scheme you are proposing or with the a'la AOLserver
limits infrastructure (per URL based) ???
Can we "bind" those limits to whatever we want? How is this working
in detail? Do you have a executive summary (in a nutshell) for me
or do I have to go to AS sources and learn all that from there?

Cheers,
Zoran