Jonathan Weedon writes :
[I apologize for slipping away from EJB and into IIOP, but it seems relevant at
this point of the debate]
> Let me be clear:
>
> 1) Context propagation is part of the GIOP specification, of which
> IIOP is the TCP mapping. Context propagation is defined.
>
> 2) The contents of a security context have not been defined for
> EJB.
Actually, it's not just that the context has not been defined, it's that there
is no room for it. If we are talking about the same thing (ServiceContextList,
defined in section 13.6.7 of the CORBA 2.3 specification), the list of legal
service IDs ranges from 0 to 9 (0 being the TransactionService). The security
context is nowhere in there.
What's worse is that the service IDs are defined by the OMG (page 13-23, :
"Each Object Service requiring implicit service-specific context to be passed
through GIOP will be allocated a unique service context ID value by OMG").
Therefore, a vendor is not allowed to, say define Service ID 10 and use it to
carry its own proprietary information.
If that's not what you are referring to, I apologize for the long email and
would be very interested to hear a suggestion that allows vendors to transmit
their proprietary data while staying fully compliant with the IIOP
specification.
> I am not trying to show that IIOP is better than anything else.
> Nor am I trying to convince you to implement your product over
> IIOP. I am simply stating that RMI-over-IIOP provides 99% of
> what is needed to provide interoperability for EJB
Keep in mind that it's not just about providing interoperability for EJB but
about offering useful and innovative features not necessarily covered by the
EJB specification (failover, clustering, etc...).
> Much better to finish a 99% solution that is based on a known,
> proven technology than to start over from scratch.
A valid recommendation but in this case, vendors do not start from scratch,
they already have their own protocol and are simply concerned that they might
have to settle for something less powerful that will make their customers
angry.
--
Cedric
===========================================================================
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".
