30 Facts About RegFree COM

The essence of RegFree COM is a language-neutral way of implementing objects that can be used in environments different from the one in which they were created, even across machine boundaries.

For well-authored components, RegFree COM allows reuse of objects with no knowledge of their internal implementation, as it forces component implementers to provide well-defined interfaces that are separated from the implementation.

The preferred method of "inheritance" within RegFree COM is the creation of sub-objects to which method "calls" are delegated.

RegFree COM is an interface technology defined and implemented as standard only on Microsoft Windows and Apple's Core Foundation 1.

For some applications, RegFree COM has been replaced at least to some extent by the Microsoft.

Related searches

RegFree COM is very similar to other component software interface technologies, such as CORBA and Enterprise JavaBeans, although each has its own strengths and weaknesses.

Text conversations and Windows messages had proved not to be flexible enough to allow sharing application features in a robust and extensible way, so RegFree COM was created as a new foundation, and OLE changed to OLE2.

RegFree COM was the major software development platform for Windows and, as such, influenced development of a number of supporting technologies.

RegFree COM replaced DDE as the preferred form of interprocess communication.

DRegFree COM extended the reach of RegFree COM from merely supporting a single user with separate applications communicating on the Windows desktop, to activating objects running under different security contexts, and on different machines across the network.

Components that made use of RegFree COM+ services were handled more directly by the added layer of RegFree COM+, in particular by operating system support for interception.

RegFree COM+ events extend the RegFree COM+ programming model to support late-bound events or method calls between the publisher or subscriber and the event system.

Nano-RegFree COM extends the native ABI of the underlying instruction architecture and OS to add support for typed object references.

Many uses of Nano-RegFree COM define two functions to address callee-allocated memory buffers as results.

Nano-RegFree COM has no notion of classes, apartments, marshaling, registration, etc.

Each RegFree COM component exposes its functionality through one or more interfaces.

All RegFree COM components implement the IUnknown interface, which exposes methods for reference counting and type conversion.

RegFree COM class is a concrete implementation of one or more interfaces, and closely resembles classes in object-oriented programming languages.

RegFree COM has support for multiple implementations of the same interface, so that clients at runtime can choose which implementation of an interface to instantiate.

RegFree COM is a runtime framework, types have to be individually identifiable and specifiable at runtime.

Each RegFree COM type is designated its own GUID for identification at runtime.

Above code fragment declares a RegFree COM class named SomeClass which implements an interface named ISomeInterface.

All RegFree COM objects utilize reference counting to manage object lifetimes.

RegFree COM objects are then responsible for freeing their own memory when the reference count drops to zero.

RegFree COM is a language agnostic binary standard that can be developed in any programming language capable of understanding and implementing its binary defined data types and interfaces.

Related searches

Registration-Free COM is a technology introduced with Windows XP that allows Component Object Model components to store activation metadata and CLSID for the component without using the registry.

In RegFree COM, threading is addressed through a concept known as apartments.

Since RegFree COM has a fairly complex implementation, programmers can be distracted by some of the "plumbing" issues.

In-process RegFree COM components are implemented in DLL files and registration only allows for a single version per CLSID, they might in some situations be subject to the "DLL Hell" effect.

Registration-free RegFree COM capability eliminates this problem for in-process components; registration-free RegFree COM is not available for out-of-process servers.