Rajiv M wrote:
BTW, Can the .so you supplied be used in production

Difficult to answer:

1) The non-debug .so is trunk code version. But trunk is *very* near to be released as 1.2.22. So I think there is no special risk, apart from the usual "it's a brand new patch release". I'm confident, that our changes were small enough, that there is only a small code risk due to the fact, that it is 1.2.22 and not 1.2.21.

2) Formally the plugin somewhere has the info, that it's version 1.2.22-dev. Someone in your organization might find out and hit you for that :)

3) the JK nsapi plugin is not used by many people. I have the impression, that the user count is slightly growing, because a couple of users asked about how to compile it in the last months. But still the user experience is very limited.

So you might run into features, that mod_jk for Apache or IIS supports fully, and which might not work for Sun Web Server. Most of the features though should work, because they are really web server independent.

Examples for features which will likely not work:

- defining uri mappings (forwarding rules) via an external file uriworkermap.propeerties
- defining uri mappings via a "mount" attribute in workers.properties
- removing the shared memory file when shutting down the web server

Conclusion:

If the production is for a business critical application and it needs to do production soon, I would use Apache with mod_jk.

If the app is not business critical or your project has a couple of weeks time, so that you and we can react on unexpected problems, and if your customer or you has some other value from using Sun Web Server, you can go that way.

On the long hand, we all don't know, how long we will support nsapi. There are plans for mod_jk 2.0 and we will then need to decide on the web servers we will proceed to support. But for the 1.2 release line we won't drop our support.

Regards,

Rainer


---------------------------------------------------------------------
To start a new topic, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to