> Hi, > > The basic tests seems to be passing on 4 platforms with different > configurations, I did some load tests and it seems to be reasonably > stable. There are certainly many small problems that need to be found, > but overall I things it looks ok. > > I would like to tag a first milestone and start using bugzilla to > track mod_jk2, and start running watchdogs and serious testing. > > While some new components may still be added ( like jk_config_registry > or jk_channel_windows, etc ), the base features should be stable. > Of course, nothing is perfect, but things are good enough for jk2.0. > > What do you think ? Nacho ? > > ( so far I tested on linux, solaris, hpux and windows, with 3.3 and > 4.0 and 4.1 - there are few tricks to get the native code to work ) > > > On a related note, we have now code to do chuid on unix - so it > would be trivial to add an option to change the user id before > the server starts processing user-code. Also it is reasonably easy > to get the signals to work - not sure this is that usefull, so > I'll not spend time on it.
I spent zero time working on the native parts of JK 2, so obviously my opinion doesn't really count ;-) I think it's good to start releasing milestones. There's already a Connector:Coyote JK 2 category in the TC 4 BZ which could be used for that. Is that good enough ? So with 4.1.x, what should be the recommended connector ? mod_jk1 or mod_jk2 ? Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
