configure options for loadable Squid modules

Hello,

        eCAP project[1] needs Squid to support loadable modules. I am adding
such support. I can see three potentially relevant ./configure options.
Please review and let me know if any of them are not really needed or
new ones should be added:

1) --with-ltdl :: This options will tell Squid to use internal ltdl
library (created by libtoolize) to handle module loading, preloading,
and unloading. I have a wrapper class from Traffic Spicer that can
handle both ltld-based and "native" dlopen operations, hiding the
difference from the rest of the code, but I am not sure we need that
flexibility in Squid. Should I assume that we will always use libtool's
ltdl and omit this option?

2) --enable-external-modules :: This option will enable support for
modules loaded runtime, from external files. There are two reasons to
have it: to disable experimental code and to build "secure" Squids that
cannot be altered by loading modules. Are these reasons enough to have
this option?

3) --enable-builtin-modules :: This option will allow the modules to
be preloaded at Squid executable linking time. Preloaded modules
simplify handling of Squid binaries because there is no dependency on
some external module file and no dangers that the external module will
not load. Should this option be named --enable-internal-modules or
--enable-preloaded-modules or even --with-preloaded-modules?

Did I miss any options?

Thank you,

Alex.
[1] http://wiki.squid-cache.org/Features/eCAP
Received on Thu Oct 11 2007 - 19:30:59 MDT