Cedric Beust wrote:
>
> The argument in a nutshell was : IIOP leaves little (if none) room for EJB
> vendors to carry their proprietary contexts (clustering, failover, etc...) at
> protocol-level.
On that point, I have to disagree 100%, because:
(a) IORs can contain proprietary profiles in addition to IIOP profiles.
(b) GIOP service context can contain proprietary tags.
<vendor>
We have been doing clustering and failover using IIOP 1.0 and 1.1 for the last
18 months. We were able to do this with standard IIOP, by using proprietary
tags that can be accomodated by IORs/IIOP. Third-party IIOP clients cannot take
advantage (yet) of the transparent automatic failover features (except on home
interfaces), but they still can benefit from load balancing.
</vendor>
________________________________________________________________________________
Evan Ireland Sybase EAServer Engineering [EMAIL PROTECTED]
Wellington, New Zealand +64 4 934-5856
===========================================================================
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".
