What Rickard is promoting is a way to not do propagation. Instead the
EJB server sends a stub to the client and the stub takes care of that.
This is a nifty cool RMI trick, but IMHO an implementation detail.
The way IIOP deals with it (as well as SOAP, DCOM and other protocols)
is through the wire. Whether your stubs do that, or someone else
generate and use their own stub and pass it on the wire is an
implementation detail.
arkin
> > The difference between my suggestion and yours is that with mine there
> > is nothing to agree upon. I propagate it my way, and everyone else uses
> > their own way. I really don't care how others do it.
>
> Can you clarify how others could interpret your contexts if you use your
> way of putting them onto the wire and everyone else uses theirs? i.e.
> how would another server know how to examine your contexts?
>
> cheers,
>
> j.
>
> ===========================================================================
> 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".
--
----------------------------------------------------------------------
Assaf Arkin www.exoffice.com
CTO, Exoffice Technologies, Inc. www.exolab.org
===========================================================================
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".
