Legacy Issue Number: 2077
Summary: Tom and I have discovered a minor outage in GIOP 1.2 relative to the
Messaging spec. The outage exists if we want to keep the door open for
publishing Messaging before GIOP is revved again. If we do not fix this
the publishing of Messaging will have to wait until the next rev of
GIOP. The outage is the following:
1) In the Request header the boolean field "response_expected" was
changed to an octet field "response_flags" in Messaging, with more
precise definition of the meanings of various flag values.
2) The Messaging spec defines a IOP::TaggedComponent for including QoS
policies in an IOR.
3) The Messaging service defines a ServiceContext for carrying QoS
policies in GIOP messages that carry ServiceContexts.
Reported: CORBA 2.0 — Tue, 13 Oct 1998 04:00 GMT
Disposition: Resolved — CORBA 2.1
Close with No change required
Updated: Sat, 7 Mar 2015 04:35 GMT
CORBA21 — A Messaging related issue in GIOP 1.2
- Key: CORBA21-108
- OMG Task Force: CORBA CORE RTF