Binary standard

from Wikipedia, the free encyclopedia
The articles binary interface and binary standard overlap thematically. Help me to better differentiate or merge the articles (→  instructions ) . To do this, take part in the relevant redundancy discussion . Please remove this module only after the redundancy has been completely processed and do not forget to include the relevant entry on the redundancy discussion page{{ Done | 1 = ~~~~}}to mark. Trustable ( discussion ) 19:04, Apr 13, 2017 (CEST)

This article was due to content flaws on the quality assurance side of the computer science editorial added. This is done in order to bring the quality of the articles from the subject area of ​​computer science to an acceptable level. Help to eliminate the shortcomings in this article and take part in the discussion !  ( + )

Reason: Dead-end article: hardly any links to other articles - Olaf Studt ( discussion ) 20:05, 15 Dec. 2016 (CET)

A binary standard is understood to be a standard in software technology that defines the data format on the lowest level. The binary standard does not allow any possible interpretation because all data (fields, variables, messages, etc.) are available in a firmly defined set. These data types are specified in byte sequences (e.g. how a string is stored in memory) and there is a fixed mechanism for how a specific block of program code is located and called.


Component Object Model (COM)

In 1993, Microsoft published the Component Object Model (COM) for reusable objects that could be used by other applications. COM offers language-independent communication between various software components. The COM model creates the prerequisites (under the Windows operating system) to address various software components in a system and to link them with other components. In addition to Object Linking and Embedding (OLE), ActiveX and DirectX are technologies that are based on the COM model.

Some technologies are built on top of COM, such as Object Linking and Embedding (OLE), which made it possible to automate applications. The versions of Visual Basic released after 1993 were designed with COM and OLE in mind. This approach was so successful that a dialect of the language, Visual Basic for Applications (VBA), was chosen as the programming language for Microsoft Office macros.

Common Object Request Broker Architecture (CORBA)

The Common Object Request Broker Architecture (CORBA) is a specification for object-oriented, application-neutral programs that mediate between application programs and that defines cross-platform protocols and services. The core of this specification is an intermediary, the Object Request Broker (ORB). In combination with an Interface Definition Language (IDL) and a binary protocol, CORBA supports the binary standard.

Object Linking and Embedding (OLE)

Object Linking and Embedding (OLE) is an object system and protocol developed by Microsoft, which is intended to enable the cooperation of different (OLE-capable) applications and thus the creation of heterogeneous composite documents. While CORBA guarantees interoperability in connection with an IDL, OLE itself defines a binary standard for access to server interfaces.

See also


  • Holger Schwichtenberg: COM component manual: System programming and scripting with COM components. Pearson Germany, 2001, ISBN 3-8273-1936-6 .
  • Peter Zöller-Greer: Software architectures, fundamentals and applications, introduction to architecture description languages ​​(ADLs). BoD - Books on Demand, 2010, ISBN 978-3-9811639-3-3 .
  • Frank Buschmann: Pattern-oriented software architecture: a pattern system, professional software development. Pearson Germany, 1998, ISBN 3-8273-1282-5 .

Individual evidence

  1. Markus Limbach: Westfälische Wilhelms-Universität Münster - Microsoft component architecture COM + and .NET framework ( Memento of the original from February 21, 2016 in the Internet Archive ) Info: The archive link was automatically inserted and not yet checked. Please check the original and archive link according to the instructions and then remove this notice. (PDF; 311 KB), 2004. @1@ 2Template: Webachiv / IABot /
  2. COM components manual: COM components for access to Windows and back office applications, accessed on February 2, 2016.
  3. Technologies of Windows Development: History of Windows Application Development, accessed on February 19, 2016.