Simplest means of setting information for a specific request which can
then be seen by a handler implemented in a different module is by
setting values in the 'notes' table of the request object.
For something more elaborate, you may need to look at using optional
functions that are exported by a module and can be looked up at run
time by another module and called.
For an example, look at the source for modules/ssl/ssl_engine_vars.c
in httpd source and the optional functions it exports as:
APR_REGISTER_OPTIONAL_FN(ssl_is_https);
APR_REGISTER_OPTIONAL_FN(ssl_var_lookup);
APR_REGISTER_OPTIONAL_FN(ssl_ext_lookup);
These can be used by another dynamic module to look up information
about requests received by HTTPS.
Graham
On 05/05/07, janmejay.tripathi <[EMAIL PROTECTED]> wrote:
Hi there,
I am currently working with apache 2.0.59. Now in the process of
writing some apache2 add-on C-module (DSO).As you know DSO Modules can
interact with the server core via the Apache2 API. Using that API each
module can access the server's data structures. Up to this I am fine. But I
have the confusion regarding InterModule (DSO Modules to DSO Modules)
communications i.e. how one DSO Module is interacting with other DSO
modules?
I think the InterModule interaction will also through Apache2 API, am I
right?
Please help me on this?
Please provide me some good sources or some documents which will help me on
this aspect.
Thanks & Regards,
Janmejay
