|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Richard M. Adler, "Emerging Standards for Component Software," Computer, vol. 28, no. 3, pp. 68-77, March, 1995. | |||
| BibTex | x | ||
| @article{ 10.1109/2.366164, author = {Richard M. Adler}, title = {Emerging Standards for Component Software}, journal ={Computer}, volume = {28}, number = {3}, issn = {0018-9162}, year = {1995}, pages = {68-77}, doi = {http://doi.ieeecomputersociety.org/10.1109/2.366164}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - Computer TI - Emerging Standards for Component Software IS - 3 SN - 0018-9162 SP68 EP77 EPD - 68-77 A1 - Richard M. Adler, PY - 1995 VL - 28 JA - Computer ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/2.366164
Software vendors have developed competing and incompatible standards to support and drive the compound document and component software technologies. These standards specify distinct object models, data storage models, and application interaction protocols. The incompatibilities have resulted in confusion in the market as vendors, users, system integrators, and developers struggle to sort out the standards' relative merits, weaknesses, and chances for commercial success. This article examines general technical concepts underlying compound documents and component software; the OpenDoc, OLE 2, COM, and CORBA standards that have been proposed for the two technologies; and the work that is underway to extend the standards and to achieve interoperability across them.
Citation:
Richard M. Adler, "Emerging Standards for Component Software," Computer, vol. 28, no. 3, pp. 68-77, March 1995, doi:10.1109/2.366164
Usage of this product signifies your acceptance of the Terms of Use.

