Hey On Sat, 31 July 1999, Jim Barton wrote: > It's important to keep in mind that RMI isn't a protocol -- it's an API. > RMI can be implemented on top of several network protocols. JRMP (the > "default") is one, T3 from WebLogic is another, and of course there is > OMG-blessed IIOP. True. > JRMP is limited in that it cannot support out-of-band information (e.g., > transactional contexts) being attached to messages, and it is not a > multi-language standard. IIOP solves both of these problems, but the issue > is finding a good vendor-supported implementation. Not entirely true. It is possible to attach transactional contexts to RMI/JRMP calls as shown by an article written by me (check my homepage for details, http://www-und.ida.liu.se/~ricob684). It uis necessary to use RMI-internal API's to do it, but I expect these to be opened up in a future release. For example, EJBoss are currently using this approach. > <vendor> > Persistence has looked at *everything* out there and chose the ObjectEra > RMI/IIOP implementation (JBroker) for its EJB server's ORB implementation. > Sun's implementation was one of the early leading candidates, but we judged > it to be too buggy and slow for serious applications. > > We ran some internal benchmarks as part of this work that I believe are > going to be made publicly available. If anyone is evaluaing ORBs and > interested in what we discovered, let me know and I'll send you our results > if/when they're ready. > </vendor> JBroker does indeed seem to be a good option. It's not free though :-( /Rickard =========================================================================== 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".
