Costin Manolache wrote:
What complexity does JNI add to jk2 ? There are separate files, using the same protocol.
The real important lesson in Jk2 is that JNI works faster and better if it is not used to pass objects.
The only 2 JNI models that actually work are jk2 "protocol marshalling, pass only byte[]" and eclipse swt "small simple calls with mostly int and byte[] params"
All that is cool, but what you propose looks a lot like JK 2 (JMX dynamic features, support for many webservers, etc), and we know that almost no developer understands it anymore. This clashes head on with the "it has to be simple" requirement: how do you expect the issue to be solved ?
This is the point about dropping server portability, among other things. Sorry to say it aloud, but for new developments I don't care about IIS (it should die) nor Apache 1.3, which are the two other servers that matter. To support these, we have mod_jk 1.2 (and too bad if people don't get the extra features).
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
