Issue 651: Issue with service context (interop) Source: (, ) Nature: Uncategorized Severity: Summary: Summary: What should an ORB do when it gets a message with an unknown service context ID value? Resolution: closed with revision Revised Text: Actions taken: August 4, 1997: received issue March 26, 1998: closed issue Discussion: End of Annotations:===== Return-Path: X-Sender: curtis@192.67.184.65 Date: Mon, 04 Aug 1997 11:47:17 -0400 To: interop@omg.org, orb_revision@omg.org, juergen@omg.org From: David Curtis Subject: issue with service context Hi, Here's a hot item: What should an ORB do when it gets a message with an unknown service context ID value? People are starting to ask for vendor-specific context tags, but there's no accommodation for this concept in the spec (that I could find anyway). All of the discussions of service context imply that service context IDs and usage will be specified by OMG. One obvious solution is to ignore such service context components. It may be useful, however, to be able to distinguish between those that can be ignored and those that can't, and raise an exception (UNKNOWN_SERVICE_CONTEXT?) in the latter case. I suspect that this is an interop RTF issue, but I thought the ORB core people might like too know about it, too. If this has already been covered, color me embarrassed. --David 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 651: Issue with service context (interop) Source: Object Management Group (Mr. David Curtis, curtis@emerald.omg.org) Nature: Uncategorized Severity: Summary: What should an ORB do when it gets a message with an unknown service context ID value? Resolution: Need discussion on the proper response. It seems ignoring the unknown service context should be allowed. If the behaviour of the service context requires the server to recognize it, it would seem to be not a well defined behaivour. Revised Text: Actions taken: Discuss whether a clarification is necessary in conference call. August 4, 1997: received issue