Costin Manolache wrote > > I can understand the jk2 "object oriented C" is considered > too complex.
True. > But I certainly can't agree on a design that is not modular > and doesn't support this basic requirement. We already have > mod_jserv and mod_webapp > - and a long history of "rewrite from scratch to make it simpler" > turning into far more complex code. > But we don't wish to write something modular and unlimitedly extendable. Just the load-balancing-ajp13+ over tcp/ip connector, for Apache2. Having that in mind, we have APR, and 'almost' a finite set of requirements, without the need to 'think modular' or 'think cross-webserver'. Lot of the code would be reusable, but it would mean that making a mod_jni connector would mean to make a completely different project without some common directory holding shareable code. Also making any additional 'features' to the connector (like 'discovery' etc.) would have to be made as such, and enabled during compile time, so that the basic functionality remains as is. This means that we don't compile everything and then use the config to either enable or disable features, but rather make something like 'mpm concept' selectable at compile time. > Seriously - if you take away the JMX and support for other > servers - why not just use mod_jserv ? No one prevents you of making mod_jmx that will allow entire Apache2 to be maintainable trough JMX console, not only our module :). Regarding other servers you meant IIS (other are less then couple of percent) probably (apache13 users can use jk). I would like to make the 'real' IIS6 filter that will go in the NT kernel's http.sys, have dynamic thread pool and MMC snap-in, but that is something completely different. Few things like config tree, ajp protocol and transport can be reused cause now we have the APR that generalizes the OS layer. If you wish to write a good Apache2 module or IIS filter, they have to be different projects. Also being usable from admins point of view requires that the apache module is configurable trough httpd.conf, and IIS trough GUI. None of them uses JMX to configure the webserver thought. I have on my dash-board for a long time a project that will make a TC as a main web server, having Apache as a 'slave' for additional PHP and Perl support, but that also is something completely different and questionably usable. > After all mod_jk and > jk2 got complex because of additional requirements and > features that we wanted to implement - if we drop them then > we can just go back and use mod_jserv. > Think that the main problem is that we don't understand the JK2 code any more, and that the modularity combined with crosswebserver became an obstacle rather then a feature. MT.
smime.p7s
Description: S/MIME cryptographic signature
