-
Key: CORBA34-156
-
Legacy Issue Number: 13105
-
Status: closed
-
Source: cs.agh.edu.pl ( Jacek Cala)
-
Summary:
There is lack of multiplex publisher port that would mimic functionality of multiplex receptacle. Having multiplex publisher port it would be easier to connect with dynamically created event consumers such that each consumer would have its own private communication channel with the publisher. In case of dynamically created consumers it is not possible to foresee the number of publisher ports required. For synchronous communication the elegant solution is a component with a multiplex receptacle for which we have separate communication channels.
-
Reported: CORBA 3.1 — Mon, 24 Nov 2008 05:00 GMT
-
Disposition: Deferred — CORBA 3.4
-
Disposition Summary:
Deferred
This proposal was generated automatically by request of the Task Force Chair Adam Mitz.
-
Updated: Wed, 1 Feb 2023 21:59 GMT
CORBA34 — There is lack of multiplex publisher port that would mimic functionality of multiplex receptacle
- Key: CORBA34-156
- OMG Task Force: CORBA 3.4 RTF