Dynamic Invocation Interface: Difference between revisions

Content deleted Content added

Inline

Revision as of 15:17, 3 January 2018

The Dynamic Invocation Interface (DII) is an API which allows dynamic construction of CORBA object invocations. It is used at compile time when a client does not have knowledge about the object it wants to invoke. With this interface an argument list is marshalled, a function is named, and a request for service is sent to the object server. DII will usually have an asynchronous mode of The following types of applications would require or benefit from DII: browsers for CORBA services, application browsers, bridges (protocol converters), applications accessing huge numbers of different interfaces, monitoring applications.

DII also provides a deferred synchronous invocation. Deferred synchronous invocations are submitted without having to wait for a response. This is similar to a one-way operation except return values and out parameters are possible, but must be polled for.

External links

This software-engineering-related article is a stub. You can help Wikipedia by expanding it.

@@ Line 1: / Line 1: @@
 {{Orphan|date=February 2009}}
-The ''' Dynamic Invocation Interface (DII) ''' is an [[API]] which allows dynamic construction of [[CORBA]] [[object (computer science)|object]] invocations. It is used at [[compiler|compile]] time when a [[client (computing)|client]] does not have knowledge about the object it wants to invoke. With this interface an argument list is marshalled, a function is named, and a request for service is sent to the object server. DII will usually have an asynchronous mode of operation.
+The ''' Dynamic Invocation Interface (DII) ''' is an [[API]] which allows dynamic construction of [[CORBA]] [[object (computer science)|object]] invocations. It is used at [[compiler|compile]] time when a [[client (computing)|client]] does not have knowledge about the object it wants to invoke. With this interface an argument list is marshalled, a function is named, and a request for service is sent to the object server. DII will usually have an asynchronous mode of
 The following types of applications would require or benefit from DII: browsers for CORBA services, application browsers, bridges (protocol converters), applications accessing huge numbers of different interfaces, monitoring applications.