> Interoperable middleware is a product of this century. It wasn't > even a dream in 1991.
IIOP appeared to be making some headway toward the end of the last century. Decent open source implementations in C++ and Java were also making some noise. My theory is the rise of SOAP came on the heels of the realization that DCOM was dead in the water, in the enterprise and especially on the Internet. XML-RPC pops up on the radar, simpler than IIOP, and moreover: it was *not* IIOP. So, XML-RPC becomes the lever Microsoft could use to avoid IIOP, and XML-RPC becomes the way vendors can peer into the Microsoft bloc. IIOP is stopped in its tracks, unfulfilled. XML-RPC becomes Simple Object Access Protocol becomes SOAP becomes WS-* (ersatz IIOP). Arguments can be made about how WS-* is better than IIOP/CORBA and I cannot argue one way or the other. They appear to be for all intents and purposes, on the same order of complexity and value. There are probably pieces of each that would lend themselves to a better whole. -Patrick ------------------------ Yahoo! Groups Sponsor --------------------~--> Check out the new improvements in Yahoo! Groups email. http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
