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

[Alexander M. <al...@gm...>]

> Looking at the Apache api, I'd be worried about using objects to duplicate their struct because there are so many fields. That could become a problem if the server was getting too much traffic
> since we don't have direct control over object de-allocation and that memory use is a concern. To compensate for that, some of the fields could be compressed if we used integers instead of strings
> where we can have defined values for different protocols, methods, etc.

> For the module why just not stick with a class of static methods for now instead of using a more complicated approach.

> Dana.


Well, I think Matthew meant "object" as a general term not specific to
instances (please correct me if I am wrong). Anyway, I agree with you
Dana that we should use static methods in this case as we otherwise
might run into memory problems if we create instances too fast.

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