Whatever specification the Object Management Group may eventually come up with in the way of Corba-to-DCOM connectivity, insiders say the whole issue is being fudged because no-one in the Corba community wants to endorse Microsoft Corp’s Distributed DCOM and there’s no-way in hell or on earth that Redmond is gonna pipe up for Corba. The same insiders, calling from OMG’s meeting taking place in Dublin, Ireland this week, say most of the ORB object request broker vendors and anyone else that’s interested are in any case hard at work hard on creating their own Corba-to-DCOM bridges. They think the wisest among the OMG community are focusing their efforts on Corba 3.0 specifications and the opportunities it will provide for creating products to capture a share of the global internet operating system infrastructure business. Corba 3.0 is slated to include the Java-based component technology, messaging, Java-to-IDL mapping, multiple interfaces, more security, the so-called CorbaBeans, a scripting language and more. The thinking is that Corba 3.0 will enable vendors to create long-overdue dynamic services on top of TCP/IP where Corba IIOP might be swapped out for messaging protocols where required – or visa versa – and object server adapters and components which can be loaded and unloaded on the fly without regard to the underlying infrastructure. One vendor said that Corba 3.0 finally recognizes the importance of server-side objects the creating of standard way of writing them. It’s like they’ve finally realized that no-one’s going to make money out of client- side technologies.
This article is from the CBROnline archive: some formatting and images may not be present.
CBR Online legacy content.