What *I* don't understand is why you think having your web container on one machine and your ejb's on another would perform better. Having your servlets run in the same JVM as your ejb's allows your servlets to access them with local interfaces, and you can pass your objects by reference instead of by value (read: serialization unecessary). You will get much better performance if everything is in the same JVM. Just beef up your box instead of spending $$$ on two.
Now, if you want to have Apache serve up some static content and front your app, that's fine (especially if for security reasons you want your app server behind a firewall and your web server in the dmz). However, it will forward dynamic requests to your app server - where your web container and ejb tier coexist in the same process.
David
--
Pavel Kolesnikov wrote:
On Wed, 20 Nov 2002, Dain wrote:There is no reason you have to separate the web container from the EJB container.
I don't understand this - what if I want to run my application on two machines because of performance reasons? What should I do instead of putting my webapp on one machine and my EJBs on the second one? Pavel
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
