-
Key: CORBA34-278
-
Legacy Issue Number: 7318
-
Status: closed
-
Source: Syracuse University ( Joncheng Kuo)
-
Summary:
The Bidirectional GIOP spec does not specify how many BI_DIR_GIOP_OFFER service contexts are allowed in a NegotiateSession or Request.
If only one such service context is allowed, it shall be stated clearly. Besides, because each BI_DIR_GIOP_OFFER service context can contain only either strong or weak BiDirIds (but not both), if there are both strong and weak BiDirIds on the ORB, the ORB has to use at least two GIOP messages to send them all.
If we allow multiple BI_DIR_GIOP_OFFER service contexts in one message, we'll have a problem in matching BI_DIR_GIOP_ACCEPT service contexts to these offers because there is no sequencing on offers and accepts.
-
Reported: CORBA 2.5 — Thu, 6 May 2004 04: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 — How many BI_DIR_GIOP_OFFER service contexts are allowed
- Key: CORBA34-278
- OMG Task Force: CORBA 3.4 RTF