Issue 1773: No way to "quench" typed event style clients... (notif_service-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: Similar to the problem described in Issue 1660 for Any-style clients, there is no way to pass quench or offer information to typed event style clients. This is because typed event style clients are either defined in CosEventComm or CosTypedEventComm, depending on the client type, and these interfaces do not inherit NotifyPublish or NotifySubscribe. Resolution: Revised Text: Actions taken: August 4, 1998: received issue February 23, 1999: closed issue Discussion: End of Annotations:===== Return-Path: From: "Michael J. Greenberg" Subject: No way to "quench" typed event style clients... To: notif_service-rtf@omg.org, issues@omg.org Date: Tue, 4 Aug 1998 16:05:26 -0400 (EDT) Cc: dsm@syl.nj.nec.com Similar to the problem described in Issue 1660 for Any-style clients, there is no way to pass quench or offer information to typed event style clients. This is because typed event style clients are either defined in CosEventComm or CosTypedEventComm, depending on the client type, and these interfaces do not inherit NotifyPublish or NotifySubscribe. To fix this problem, the input parameters to the connect_* operations that are currently scoped to CosEventComm should be changed to CosNotifyComm. In addition, to accommodate the connect_* operations whose input parameter is scoped to type CosTypedEventComm, it will be necessary to define a CosTypedNotifyComm module that defines correponding typed client interfaces that also inherit NotifyPublish or NotifySubscribe. I have a proposal in mind to fix this problem, and will circulate it shortly. Regards, Mike -- Michael J. Greenberg NEC Systems Lab. 4 Independence Way Tel. 609-734-6142 Princeton, NJ 08540 Fax. 609-734-6001 mjg@syl.nj.nec.com