On Tue, 4 Jun 2002, Mladen Turk wrote: > We are talking _apache_ modules true? > They extends the _apache_ server, so one writing one should be familiar > with the .conf I think. > In theory some functionality could be reused on other servers like > authentication, and I'm not sure I want to do that, but you never know > :)
Support for other servers is already built into jk, and even if you ( or me ) are mainly using Apache, there are people who have to support other servers. I think an auth module would be far more usefull if it would work on any server - probably not as good as in apache, but it would allow people to migrate or support existing infrastructures. Besides, many java programmers are not that familiar with the .conf file. Please note that the current jk2 is designed very much like tomcat - a collection of components ( beans ), configurable at runtime, the config file is abstracted, etc. It shouldn't matter how you configure - what's important is to follow some patterns ( JMX-like if you want - named components with attributes ). Runtime reconfiguration is much more important - while gracefull restart works great, a servlet environment will have too many changes ( webapps deployed/undeployed, lb workers going up and down, etc ) - and in apache2 ( with multithreaded mpms ) the price for restart may be higher ( since it may lose state or require in-process java VMs to restart and lose sessions ). > I'll try to work-out something this week. > For start I'd like to reorganize the mod_jk2 by putting needed includes > in the jk_apache2.h and adding > external module AP_MODULE_DECLARE_DATA jk2_module in it. > If that's ok with you. > The reason for that is that I would like to put the extended > functionality in the separate file. That's fine. You can also start with a different dir - and merge later. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
