Tomcat mod_jk was written by Gal Shachor :
"Gal Shachor is a research staff member at IBM.
He wrote his first Servlet container
(ServletExpress) at the beginning of 1997.
Later on ServletExpress (and Gal) merged into WebSphere,
and Gal participated in the development of WebSphere 1, 2 and 3."
And if you play with AS/400 like me, you also discover
that Websphere use also mod_jk (with jni).
Another proof that mod_jk is really very portable :)
-
Henri Gomez ___[_]____
EMAIL : [EMAIL PROTECTED] (. .)
PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
>-----Original Message-----
>From: Milt Epstein [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, April 19, 2001 11:09 PM
>To: '[EMAIL PROTECTED]'
>Subject: RE: Tomcat vs. other app servers
>
>
>On Thu, 19 Apr 2001, Jann VanOver wrote:
>
>> FYI: if anyone is interested in joining the JRUN-talk group, you can
>> sign up at http://www.houseoffusion.com click on the <MAILING LIST>
>> link on the left
>
>As long as you've reposted this note of mine :-), I should take the
>opportunity to correct myself. It was actually ServletExec (from New
>Atlanta) that I had used (with NES) before switching to Tomcat/Apache,
>not JRun. Don't know what I was thinking when I wrote that :-).
>
>I had evaluated both ServletExec and JRun. They seemed similar in
>terms of functionality and performance. I went with ServletExec
>because it was easier to set up, and because their support was *much*
>better. They have a mailing list where the ServletExec/New Atlanta
>people are *very* responsive. This is running on AIX, FWIW.
>
>
>> -----Original Message-----
>> From: Milt Epstein [mailto:[EMAIL PROTECTED]]
>> Sent: Thursday, April 19, 2001 3:35 AM
>> To: [EMAIL PROTECTED]
>> Subject: Re: Tomcat vs. other app servers
>>
>>
>> On Thu, 19 Apr 2001, Jeff Turner wrote:
>>
>> > We have found JRun 3.0 to be a fine product (as was it's 2.3
>> > predecessor), and use it in many production environments.
>One should
>> > be careful to avoid unsubstantiated claims on this forum, lest it
>> > amount to FUD.
>> >
>> > That said, most of our developers use Tomcat for development. It is
>> > spec-compliant, doesn't crash, has excellent support (this list:)
>> > and 3.3/4.0 eliminates much classpath pain. By contrast, JRun
>> > *extends* the spec, accepting invalid syntax (like <%= foo; %>)
>> > which means JSP authors must constantly be on guard to avoid
>> > portability problems. JRun does not have a tomcat-users equivalent,
>> > thus has effectively no user community. Unless you're a fan of
>> > phone-based support, that doesn't leave one much recourse when help
>> > is needed.
>> [ ... ]
>>
>> JRun does/did have a JRun-talk mailing list. There was participation
>> by Allaire/JRun people, but it was a little strange, they seemed to
>> disclaim it as a support forum (it was a support forum when
>it started
>> out, before Allaire took over JRun). Anyway, it wasn't as useful as
>> this list. They also have some online/web-based fora, but I never
>> used those.
>>
>> I had used JRun (2.2), along with Netscape Enterprise Server, before
>> switching to Tomcat/Apache some time back. It worked fine for us.
>[ ... ]
>
>Milt Epstein
>Research Programmer
>Software/Systems Development Group
>Computing and Communications Services Office (CCSO)
>University of Illinois at Urbana-Champaign (UIUC)
>[EMAIL PROTECTED]
>
