Legacy Issue Number: 2917
Source: Ericsson ( Neill Jones)
There is an assumption in the design that there is a one to one
association between a TcPduUser and a TcPduProvider
during a TC Session. This is enforced in the IDL through the
and the factory call
in TcPduUser user,
out DialogId d_id)
Since the TcPduUser reference (or some sort of reference)
is not passed over in get_dialog_id(), the only conclusion
is that the reference has to be the one passed over in the
create, and therefore that each TcPduProvider is tied to
one and only one TcPduUser.
Reported: CORBA 2.3.1 — Wed, 22 Sep 1999 04:00 GMT
Disposition: Deferred — CORBA 3.4
This proposal was generated automatically by request of the Task Force Chair Adam Mitz.
Updated: Wed, 1 Feb 2023 21:59 GMT
CORBA34 — Why one to one association between a TcPduUser and TcPduProvider interface?
- Key: CORBA34-313
- OMG Task Force: CORBA 3.4 RTF