Re: Re[2]: [insomnia-httpd-devel] Module System

[Matthew C. <mpc...@li...>]

Sounds good. Let me know when you have the interface worked out and I
will have a go with writing a cache module - probably something simple
to start with.

Also it's clearly not as simple as just having the same request call
being passed into each module in turn - as some modules such as gzip or
cache would really need to be processing the output of another module
like the cgi-processor (unless they intend to resubmit the request to
another module internally - which doesn't sound ideal).

Regards,
Matt.
> What I imagined is a module class which implements an insomnia module
> interface providing generic communication methods for the core. Upon
> startup every module is initialised by the core and added to a module
> manager. So far I do not see any problems, however it gets more tricky
> handling the actual requests. We do not only have to pay attention to
> the order in which the module are invoked (eg: a GZIP module has to
> run as last one) but also that several modules must not process the
> same output.
> 
> Alexander
> 
> 
> 
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
> 
> _______________________________________________
> insomnia-httpd-devel mailing list
> ins...@li...
> https://lists.sourceforge.net/lists/listinfo/insomnia-httpd-devel