Java is an interpreter that reads bytecodes generated by javac (the java
compiler) and at runtime converts those bytecodes into machine instructions.
Apache is a natively compiled executable designed for one specific purpose -
serving web content quickly. If you create a module that "is" Apache, it
would have to run under the Java interpreter, and could thus not possibly
approach the performance of a natively compiled Apache.
Now, you may argue that in the era of 2 GHz CPUs, the difference might
become unnoticeable. That is an armchair debate. By the way, Tomcat
already comes with a web server built in, so you don't need Apache at all if
you are content with the functionality and performance of the Tomcat's web
server.
----- Original Message -----
From: "Richard Bottoms" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 22, 2001 2:13 AM
Subject: Re: [JBoss-user] Apache+Tomcat+JBoss
> My business partner wondered why the goal is to send static pages out to
> Apache when it might make more sense to create a module that 'is' Apache
> inside the JBoss-tomcat space.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
