Issue 3184: Allow GIOP 1.3 messages to be transported. (incorba-ftf) Source: Siemens AG (Mr. Nils Fischbeck, ) Nature: Uncategorized Issue Severity: Summary: Align SIOP definition with GIOP 1.3 of CORBA2.3.1. Problem: SIOP is currently defined to carry GIOP messages with version 1.2 and lower. Proposed Solution: Allow GIOP 1.3 messages to be transported. Resolution: Revised Text: Actions taken: January 7, 2000: received issue Discussion: End of Annotations:===== From: Fischbeck Nils To: "'Boldt, Juergen'" Subject: Issue Incorba-ftf Date: Fri, 7 Jan 2000 17:54:06 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain X-UIDL: i9,!!;JDe9MYTd9X4Be9 Hello Juergen, I have the following issue for the IN-Corba FTF: Align SIOP definition with GIOP 1.3 of CORBA2.3.1. Problem: SIOP is currently defined to carry GIOP messages with version 1.2 and lower. Proposed Solution: Allow GIOP 1.3 messages to be transported. Regards Nils --- Nils Fischbeck +49 03834 555 8178 SIEMENS AG, ICN WN AN AM46 New E-mail address: Nils.Fischbeck@icn.siemens.de From: Fischbeck Nils To: incorba-ftf@emerald.omg.org Subject: Issue #3184 Date: Tue, 11 Jan 2000 09:05:52 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain X-UIDL: )K3!!3%nd9i=Ce9I@U!! This issue asks for alignment for the SIOP spec with CORBA2.3.1. There the GIOP version is 1.2 not 1.3 as mentioned in the issue statement itself. Rob did already an excellent Job in bringing the GIOP version 1.2 into the spec. However I have some minor corrections. 1. SIOP should have the same version as GIOP. So I propose to define SIOP 1.2 instead of SIOP 1.0. 2. The BiDirectional GIOP is used in SIOP by default (but this has no implications). I would like to state this fact also in the spec. Therefore I propose the following changes: page 95: Replace SIOP version 1.0 clients ... with SIOP version 1.2 clients ... SIOP version 1.0 server ... with SIOP version 1.2 server .... page 97: Replace SIOP specified here has a major version 1 and a minor version 0. with SIOP specified here has a major version 1 and a minor version 2. page 98: Replace However, it is not an error that the server sends a GIOP CloseConnection message. with However, it is not an error that one side sends a GIOP CloseConnection message. page 99: After The clients are informed with a COMM_FAILURE exception if appropriate. add Since SCCP is connection-less bi-directional GIOP is used by default. No special IOP::ServiceContext is defined (ie. no BiDirSIOPServiceContext). Setting a BidirectionalPolicy has no effect. Regards Nils --- Nils Fischbeck +49 03834 555 8178 SIEMENS AG, ICN WN AN AM46 New E-mail address: Nils.Fischbeck@icn.siemens.de From: "Rob Brennan" To: "ftf" Cc: "Nils Fischbeck" , "Dave Stringer" , "Stephen Brennan" , "Nilo Mitra (EUS)" , , Subject: IN/CORBA - Issue 3184 VOTE Date: Tue, 25 Jan 2000 11:40:48 -0000 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1154 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1 X-UIDL: 'ai!!?G[d9^I\d98;)!! Hi All, happy new year to everyone! I propose the following resolution for issue 3184 (as per Nils' email): Please return a vote to me (brennanr@teltec.dcu.ie) by 12 PM GMT JANUARY 28th 2000 Voting lists, issues, resolutions etc can be found from the IN/CORBA FTF Home at: http://www.teltec.dcu.ie/~brennanr/incorba-ftf/ ****Please remember that if you consistently fail to vote you lose the power to vote.**** BEGIN PROPOSED RESOLUTION page 95: Replace SIOP version 1.0 clients ... with SIOP version 1.2 clients ... SIOP version 1.0 server ... with SIOP version 1.2 server .... page 97: Replace SIOP specified here has a major version 1 and a minor version 0. with SIOP specified here has a major version 1 and a minor version 2. page 98: Replace However, it is not an error that the server sends a GIOP CloseConnection message. with However, it is not an error that one side sends a GIOP CloseConnection message. page 99: After The clients are informed with a COMM_FAILURE exception if appropriate. add Since SCCP is connection-less bi-directional GIOP is used by default. No special IOP::ServiceContext is defined (ie. no BiDirSIOPServiceContext). Setting a BidirectionalPolicy has no effect. END PROPOSED RESOLUTION