Lists Home |
Date Index |
- From: "Anders W. Tell" <email@example.com>
- To: Didier PH Martin <firstname.lastname@example.org>
- Date: Mon, 05 Apr 1999 10:33:42 +0200
To make a long story short, Corba does NOT support what I call
"Component Binary Interface" CBI for short. This is what Microsoft have
implemented within their COM. Some Corba's have however implemented
"colocation" which is a shortcut route so marshalling is not performed
when calling objects within the same adress space.
See <http://www.cs.wustl.edu/~schmidt/TAO.html> for an example.
Here is a list of implementation options (faster to slower)
1.Private Component calls (not calling across Interfaces)
No time penalty, same as normal C or C++ calls
2.Public Interface calls (calling other components using interface pointers)
Same as C++ virtual function calls, slightly slower than above
The MS COM and Mozilla way.
3.Optimized In-process Collocation call, to a Corba Object Adapter (OA)
Call routed directly to object. This is outside the Corba spec.
4.In-process Collocation call, to a Corba OA managed object
No marshaling, but call put in queue or rerouted by OA according to Corba guidelines.
Corba Components implemented in same language.
5.Process to Process call, using Corba OA's
Parameter marshaling and IIOP calls.
Corba Components may be implemented in different languages.
6.Inter Machine Process to Process call, using Corba OA's
Parameter marshaling, IIOP calls and network traffic.
/ Financial Toolsmiths AB /
/ Anders W. Tell /
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)