Hi Laird
what I mean is that if you know some of the EJBs are only ever called
locally then you can ignore all the design idioms for distributed objects.
But for truly remote calls the idioms must be followed. That's what I mean
by having to *design* two types of 'remote' interface. I know the
containers optimise local calls - just as CORBA has been doing for years.
I'm less interested in the runtime issues, the container takes care of it.
Its the design phase of it that interests me more. Developers would need to
know if EJBs were to be called locally only, or mostly local but
occasionally remotely etc etc We'd end up having to document at method
level whether or not remote calls would be made.
regards
Mike
At 19:05 30/03/00 -0500, you wrote:
>Mike Swainston-Rainford wrote:
> >
> > Hi Laird
> >
> > true, but what this means in practice is that you have to design two types
> > of remote interfaces, ones that will be called from outside the container
> > and ones that will actually be local.
>
>Nope; container handles this automatically. See the source code of one
>container that does this (http://www.ejboss.org/).
>
>Cheers,
>Laird
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
