Issue 2263: reply handler object in the AMI model (messaging-rtf) Source: (, ) Nature: Clarification Severity: Summary: Summary: It does not appear to be clear in the AMI model whether in a non TII mode, a reply handler object can be one outside the process which issued the AMI request. For example, in section 3.3.1 AMI Components ReplyHandler - A ReplyHandler is an Object which encapsulates the functionality for handling an asynchronous reply. It is used for callback model reply handling. and then in section 3.3.2 TII Components Persistent Reply Handler - A ReplyHandler whose Object reference is created by a POA with a PERSISTENT LifeSpan Policy. The Persistent Reply Handler may be implemented by a process other than the one that issued the request. Resolution: close this issue Revised Text: Actions taken: December 17, 1998: received issue January 9, 2001: closed issue Discussion: It is sufficiently clear that a reply handler can be outside the process whch issued the AMI request. Close this issue. End of Annotations:===== Return-Path: From: Chris Smith Date: Thu, 17 Dec 1998 15:39:09 +0100 To: messaging-rtf@omg.org, issues@omg.org Subject: Further Messaging Clarification X-Sun-Charset: ISO-8859-1 It does not appear to be clear in the AMI model whether in a non TII mode, a reply handler object can be one outside the process which issued the AMI request. For example, in section 3.3.1 AMI Components ReplyHandler - A ReplyHandler is an Object which encapsulates the functionality for handling an asynchronous reply. It is used for callback model reply handling. and then in section 3.3.2 TII Components Persistent Reply Handler - A ReplyHandler whose Object reference is created by a POA with a PERSISTENT LifeSpan Policy. The Persistent Reply Handler may be implemented by a process other than the one that issued the request. But nowhere (that I can find) in the spec does it say (as I believe it probably should) that a regular ReplyHandler MUST be implemented in the same process as that which issued request, and more importantly, it does not say how such an action would be detected, and what exception would be thrown to who. Regards Chris Smith ------------------------------------------------------------------------- Software Designer & OMG Standards Ericsson Utvecklings AB Tel : +46 8 727 5726 Box 1505 Fax : +46 8 647 8276 S12525 Dlvsjv Email : Chris.Smith@uab.ericsson.se Sweden