----- Original Message -----
From: "Rickard �berg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, February 13, 2000 8:15 AM
Subject: RMI-IIOP only? was Re: How to get a container to know what
Principal iscalling it?
> This touches upon an interesting subject:
> Is it possible to deploy a bean and make it accessible through many
> protocols? If not, then any server that uses a protocol that is more
> optimized than IIOP, such as WLS, will have degraded performance if
> RMI-IIOP is mandated.
> IMHO I don't think it's possible to make a bean accessible through
> several protocols simultaneously. Why not? Because, what would be the
> result of the Handle.getEJBObject and *Context.getEJBObject()? Should
> the stubs returned be able to support several protocols? If not, which
> one should it be: the native one or a stub that supports IIOP? Either
> way you run into trouble.
By running into trouble I take you mean either one can't propagate context
or one has to take a performance hit to convert to an interoperable
protocol.
I would certainly like to be able to choose from among all protocols
supported
by a given server. Interoperabillity should not need to rely on support at
the
wire protocol layer, which I believe is your next point.
> IMHO a better way to introduce interoperability is to have API's that
> lets a stub figure out which security id and tx id is associated with
> the current thread. This way that information can be extracted and
> forwarded in any way it pleases. The only requirement is that the client
> has installed the packages needed to support the stubs of the server.
> This will of course make it troublesome to be able to call a server from
> a C++ client, but in those cases I would simply use a server that indeed
> uses IIOP as protocol. We would still have interoperability between EJB
> servers.
This I totally agree with this.
> Comments? If RMI-IIOP is mandated *and* my fear that it is only possible
> to have one protocol at a time, EJB-servers will be severely restricted
> in the ways it may provide cool functionality, such as transparent
> fault-tolerance and load-balancing.
There has to be some base interoperability wire protocol that all servers
are guarenteed to support doesn't there? In addition to this, having the
capability to choose an alternate protocol and still have context
transmission
using container-container APIs is a desirable feature.
===========================================================================
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".
