Rickard �berg [[EMAIL PROTECTED]] wrote:
> I believe you are missing the point. I am not arguing
> whether IIOP is a bad protocol or not. In fact, even
> if everything worked perfectly with IIOP, i.e. security
> context propagation was defined and all that, I think
> it would be a mistake to use it. IIOP as such is
> irrelevant in the case I am making.
>
> What I am opposed to is the general approach to the
> problem. The problem is how to do multi-vendor server
> interoperability. As I have, in great detail, explained
> there are (at least) two possible solutions. One is to
> choose a wire-protocol. One is to choose an API-based
> solution. The case I made was that regardless of the
> wire-protocol chosen, it is a worse solution than the
> second one. I have clearly explained why I think so,
> and will not re-iterate.
Now I'm confused. How does specifying the communication API guarantee that
two implementers of the same API will be able to talk?
> In my humble opinion, it seems you have been looking at
> the problem for too long, and can't see the forest for
> all the trees. You would do well to step back a bit and
> reconsider the new landscape. In my opinion, you are
> thinking in ways of CORBA and inter-platform
> interoperability. This is not the case here, as the
> platform is only one, namely J2EE. It seems you consider
> the new landscape to be the same as the old one. It is
> not. It is new, and have new opportunities, which we
> should embrace in order to enhance EJB, and its usage,
> as much as possible.
To think the new order is only J2EE seems short-sighted. In a twinkling of
an eye, it will be CCM (CORBA Component Model). Even Sun thinks this, which
leads us back to IIOP. This is why [I think] everyone is trying to 'fix'
IIOP to work in the new order.
Jeff
===========================================================================
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".
