that would be the only case where I can see that you could bypass RMI. How
it would be done and maintain within spec would be beyond me. since the
client is not run in the container... certainly in the case of a session
bean calling Entities yes, but in the case of a web client (servlet or
whatever) calling the session bean you are still going to have the RMI
overhead. That was my contention. I assumed Karl was speaking of the
inter-container calls between Session and Entity beans when he referred to
them not being called remotely.... after I thought about it :)
Al
----- Original Message -----
From: "Steven Punte" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Sunday, May 28, 2000 7:33 PM
Subject: Does Orion eliminate RMI? Was: How are database JOINS achieved with
EJBs?
>
> > Al Fogleson wrote:
> > > then you start adding all the RMI calls over the network and that adds
> > some load too
> >
> > Well, EJBs will not always be called remotely to start with. A very
> > common scenario is that you write Servlets/JSPs that communicate with
> > EJBs. Usually you will run your Web components and EJBs on the same
> > servr and no RMI calls will be made. Of course though, if you need the
> > remote access it will be used. But that is an overhead you need no
> > matter what technology. Orion's RMI-transport protocol is very
> > optimized.
>
> I agree with Karl that RMI, even on the same machine, is a significant
> overhead. Think of CPU consumption to serialized and de-serialize
> member function arguments and return value.
>
> When ones' client and EJB container are both on the same machine
> and in the same process, CAN Orion bypass the RMI protocol
> here and achieve near optimum performance?
>
> It would be like having your cake and eating it too, to have both
> the Enterprise architecture and near optimum performance
> in this single server scenario. :-)
>
> STeve
>
>
>
>
>
