On Wednesday 15 December 2004 18:29, Stas Bekman wrote:
Should we link to this kind of extension modules from the Apache::Connection manpage? http://perl.apache.org/docs/2.0/api/Apache/Connection.html e.g. a new section 3rd party modules extensions? or will this become a maintenance hell if many of those start to pop-up?
Well, I think it would be useful to do it. But I would place restrictions on the kind of modules mentioned there. Maybe a good start are modules that provide access to exported functions of apache core modules (that are shipped with apache). I could think of a module interfacing mod_includes' ap_register_include_handler() for example to reenable <!--#perl ... --> directives to be qualified for being linked. But my Apache::ClickPath would not qualify.
I like your suggestion, Torsten. Still should we put all 3rd party extensions into a single page, somewhere under
http://perl.apache.org/docs/2.0/api/index.html
like, "3rd party Modules that Interface the Apache2 API". I think this will be the most suitable, since while we can mention Apache-ModSSL in the
Apache/Connection.html, things like mod_include glue don't already have a manpage.
If you agree with this approach, could you start with creating such a pod and add yours and any other relevant existing modules and also explain in the Description that only modules that provide glue for the Apache API (core and its modules) are listed in that document.
thanks.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
