-
Key: CORBA23-168
-
Legacy Issue Number: 2940
-
Status: closed
-
Source: Cisco Systems ( Paul Kyzivat)
-
Summary:
Something seems unclear to me about how to interpret a RequestHeader_1_2
when the AddressingDisposition of the TargetAddress is ReferenceAddr:In the case the request contains a full IOR, which may have several
profiles. Since each profile has its own object_key, and there is no
requirement that they all be the same, the key for the operation may
depend on which profile chosen.The client had to choose some profile in order to send the request, but
that information is not included in the request. So apparently the
server must decide on its own which profile it would like to use. This
may not be the same one the client chose.What if any requirements are there on how this is done?
-
Reported: CORBA 2.3 — Wed, 22 Sep 1999 04:00 GMT
-
Disposition: Resolved — CORBA 2.3.1
-
Disposition Summary:
withdrawn by submitter...issue closed
-
Updated: Fri, 6 Mar 2015 20:58 GMT
CORBA23 — Need clarification on GIOP::TargetAddress
- Key: CORBA23-168
- OMG Task Force: CORBA Core 2.3 RTF