Not much to add, but for the record..
> My understanding of the central issue under discussion: whether a
> wire protocol or API solution to context propogation is superior.
> IIOP's ability to do the job might be relevant here, but Rickard's last
< post on this discussion (that I received--the listserv has been acting
> up lately, I think) specifically disclaimed an attempt to discredit
.. this is correct..
> I am very interested in your arguments as to the superiority of a
> protocol-based solution, and I mean that sincerely. I am not an
> EJB vendor. I'm a software developer who is interested in the future
> of EJB.
.. I am an EJB-vendor (and an EJB-developer, and an EJB-theorist, and a
pragmatic person, etc.), but whenever I post here my opinions are always
in this order:
1. What's best for EJB in the long term
2. What's best for my own server, EJBoss
3. What's best for all other vendors' servers
1 and 2 never change place.
And..
> A stub from a server using RMI-JRMP would still extract
> information from the container using a standard API, but it could
> propogate the transaction in a proprietary way. This would not
> effect interoperability.
.. this is the core of an API-based solution, and..
> But like I said, I have no reason apart from technical superiority to
> root for one solution over another. I'm interested in a continuing
> dialog that addresses technical issues.
.. I agree with this :-)
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
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".
