Issue 593: CloseConnection messages (interop) Source: (, ) Nature: Uncategorized Severity: Summary: Summary: 1.1 client may get 1.0 CloseConnection prior to first attemptto send Requests which it needs to recognize. Spec should clarify this. Resolution: closed with revised text Revised Text: Actions taken: June 17, 1997: received issue March 26, 1998: closed issue Discussion: End of Annotations:===== Return-Path: Date: Wed, 10 Dec 1997 16:49:32 -0500 From: ter@holta.ho.lucent.com (T E Rutt) To: interop@omg.org Subject: Interop 1.2 RTF Conference call (Proposed revisions and issues) To: Interop 1.2 RTF Subject: Dec 19, Conference Call From: Tom Rutt, RTF Chair I have attached my proposed Resolutions of Issues for ORB Interoperability 1.2 Revision Task Force. There was no meeting of the RTF at the NJ meeting, since everyone is so busy I decided to take a whack at coming up with resolutions for the issues. We need further discussion on some of these issues, as indicated in the actions section of each issue. A conference Call is scheduled for Friday, December 19, at 11:00 EST. I have the bridge reserved for 2 hours. The bridge phone number (16 ports reserved) is: +1 630 224 444 Conference Code 674 369 Let me know if you will participate, so I can ensure 16 is enough ports. Tom Rutt Issue 593: CloseConnection messages (interop) Source: IONA (Mr. Craig Ryan, cryan@iona.com) Nature: Uncategorized Severity: Summary: 1.1 client may get 1.0 CloseConnection prior to first attemptto send Requests which it needs to recognize. Spec should clarify this. Resolution: Support of 1.1 version would also require support of 1.0 if backwards compatiblity is desired. It seems odd that an ORB would support 1.1 and not 1.0 GIOP version. Revised Text: Actions taken: Need discussion on why GIOP 1.1 implementations would not also support GIOP 1.0 messages. June 17, 1997: received issue