-
Key: NOT11-13
-
Legacy Issue Number: 1660
-
Status: closed
-
Source: Anonymous
-
Summary:
Summary: In the CosNotifyComm module, we define new client interfaces for clients
that supply and consumer structured events and sequence of structured events.
In the CosNotifyChannelAdmin module, we define different proxy interfaces
for clients that deal with Anys, structured events, and sequences of
structured events. For the proxies that deal with Anys, we rely on
Event tyle clients to connect to them. In other words, the input parameter
to the "connect_*" operations defined on the proxies provided for clients
that deal with Anys are of a type defined in the CosEventComm module. This
is because we don"t redefine Notification-specific interfaces for clients
that deal with Anys.It has just occurred to us that this makes it impossible to propagate
"subscription_change" requests to clients that deal with Anys. This is
because such clients are defined in CosEventComm, and do not support
the NotifySubscribe or NotifyPublish interfaces. -
Reported: NOT 1.0.1 — Fri, 10 Jul 1998 04:00 GMT
-
Disposition: Resolved — NOT 1.1
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
NOT11 — No way to "quench" to event style supplier
- Key: NOT11-13
- OMG Task Force: Notification Service RTF