Distributed object computing (DOC) has received a substantial amount of attention over the past several years. DOC uses OO techniques to distribute reusable services and applications over multiple, often heterogeneous, computing and networking elements. The most widely publicized DOC tools are based on OMG's CORBA, Microsoft's Distributed COM (DCOM), and JavaSoft's Java Remote Method Invocation (RMI).
With potentially lucrative technologies like DOC, there are always opportunists who ``ride the wave'' to further their careers, regardless of whether they truly understand or support the technology. Over the past decade, I've witnessed this phenomenon with AI expert systems, CASE tools, OO methods, software process maturity models, C++, frameworks, components, patterns, and Java. It's remarkable to watch the same opportunists re-position themselves time and again, with every change in technological fashion and fortune.
Recently I've spoken with several notable technologists who feel that the hype associated with DOC technologies is yet another example of the triumph of marketing over technology. While I share their distain for the shameless hucksterism surrounding DOC, I don't think it's quite as easy to dismiss distributed object computing as it was to dismiss earlier generations of over-hyped technologies like CASE tools. Here's why:
This issue of C++ Report contains three articles that focus on CORBA. Jennifer Hamilton describes the use of Distributed SOM's ``DirectToSOM'' C++ compiler; Steve Vinoski and I present an overview of the CORBA Events Service; and Rocky Stewart, James Storey, and Dehua Huang illustrate how they've enhanced the CORBA Events Service and applied it to a commercial CORBA-based telecommunications management system. We'll be covering other C++ DOC technologies, in particular DCOM, in subsequent issues of the C++ Report.
Back to C++ Report Editorials home page.
Last modified 18:06:19 CST 25 January 2019