Issue 2077: A Messaging related issue in GIOP 1.2 (interop) Source: (, ) Nature: Uncategorized Issue Severity: Summary: 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. Resolution: Close with No change required Revised Text: Text was incorporated into Corba 2.3, as directed in interop rtf report 98-07-01. Actions taken: October 13, 1998: received issue October 13, 1998: closed issue Discussion: End of Annotations:===== Return-Path: Sender: jis@fpk.hp.com Date: Tue, 13 Oct 1998 11:11:28 -0400 From: Jishnu Mukerji Organization: Hewlett-Packard New Jersey Laboratories To: interop@omg.org Cc: Tom Rutt , Jon Goldberg Subject: A Messaging related issue in GIOP 1.2 Folks, 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. If we want to leave the door open for publishing the Messaging spec before GIOP is revved again, we need to incorporate place holders for these three in GIOP 1.2 with pointers to the adopted (but yet to be formally published) Messaging spec. Of these, only (1) is of immediate importance, since it will be difficult to incorproate this after the current edit cycle before CORBA 2.3 with GIOP 1.2 is published. If you would like to see what changes need to be made to Chapter 13 and 15 of CORBA 2.3 to incorporate these drop me a line, and I will post the necessary changes. They are not very large. Any thoughts on this matter from the experts? Thanks, Jishnu. -- Jishnu Mukerji Systems Architect Advanced Development Enterprise Internet Solution Center Enterprise Systems Group Email: jis@fpk.hp.com Hewlett-Packard New Jersey Labs, Tel: +1 973 443 7528 300 Campus Drive, 2E-62, Fax: +1 973 443 7422 Florham Park, NJ 07932, USA.