It is my understanding that calls to remote interfaces, when run in the same VM, used an optimized, emulated local path...
So, you can design against remote interfaces but still get lots of speed... Otherwise everything would be done using RMI... Slow.... One of my apps uses local interfaces now, which is working well for us. If we need more, the JBoss3 clustering will pick up the slack. Hunter > From: Mark Gulbrandsen <[EMAIL PROTECTED]> > Date: Fri, 29 Mar 2002 09:28:47 -0700 (MST) > To: <[EMAIL PROTECTED]> > Subject: Re: [JBoss-user] better to run Tomcat and JBOSS seperately? > > > Does jndi realize that its requests are all in-VM, or do you have to > configure it using local interfaces rather than remote interfaces? I mean, > do you have to write the client using the local home and local interface > rather than the remote home and remote interface. > > Isn't using local interfaces tying you into a non-scalable architecture? > Or are you thinking of clustering the jboss/tomcat nodes to achieve the > scalability? > > Regards, > > Mark > > On Thu, 28 Mar 2002, Hunter Hillegas wrote: > >> The main advantage of having them integrated is SPEED. It is SO much faster >> that way as communication between the web tier and the EJB tier doesn�t have >> to go across the wire, it is all in-VM. >> > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
