---
title: Dynamic Invocation Interface
slug: dynamic-invocation-interface
qid: 
snapshot: enwiki-001344561359
content_hash: 
license: CC BY-SA 4.0
source: https://en.wikipedia.org/w/index.php?oldid=1344561359
tags: [100393015, 20340897, 23118434, 23468805, 23603337, 24043274, 59695247]
---

# Dynamic Invocation Interface

> [!note] Provenance
> Snapshot `enwiki-001344561359` · content root `…`
> Derived from <https://en.wikipedia.org/w/index.php?oldid=1344561359> · Licensed CC BY-SA 4.0

The Dynamic Invocation Interface (DII) is a CORBA API that allows clients to construct and invoke object requests dynamically at runtime, without requiring compile-time knowledge of the target interface. Using DII, a client specifies the operation name, builds and marshals the argument list, and sends a request to the object via the ORB. DII supports several invocation modes, including synchronous and deferred synchronous invocation. It is particularly useful for applications such as CORBA service browsers, protocol bridges, systems interacting with many different interfaces, and monitoring tools. In deferred synchronous invocation, a request is sent without blocking for a response. Unlike one-way operations, return values and out parameters are available, but the client must explicitly poll for completion and retrieve the results.

The Dynamic Invocation Interface (DII) is a CORBA API that allows clients to construct and invoke object requests dynamically at runtime, without requiring compile-time knowledge of the target interface. Using DII, a client specifies the operation name, builds and marshals the argument list, and sends a request to the object via the ORB. DII supports several invocation modes, including synchronous and deferred synchronous invocation. It is particularly useful for applications such as CORBA service browsers, protocol bridges, systems interacting with many different interfaces, and monitoring tools. In deferred synchronous invocation, a request is sent without blocking for a response. Unlike one-way operations, return values and out parameters are available, but the client must explicitly poll for completion and retrieve the results. ==References==
