Issue 3518: Issue with pushing events (notif_service-rtf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: 2. Publishers are allowed to push events for the types they have not offered using offer_change(). 
This can allow publishers to never advertise the event types they are offerring.  For Example, as 
a consumer it can not tell what are the event types that will be offered on the channel. 

Can we require publishers to always call offer_change() on the new event types before pushing them to 
the event channel?  If this behavior breaks existing functionality, then how about having push_xxx()
check to see if the event type is offered, if not add it to the aggregate list?

Resolution: 
Revised Text: 
Actions taken:
March 30, 2000: received issue
Discussion: 

End of Annotations:=====
X-Sender: siegel@192.67.184.65
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 30 Mar 2000 12:07:09 -0500
To: issues@omg.org
From: dora.2.potluri@mail.sprint.com (by way of Jon Siegel
<siegel@omg.org>)
Subject: Notification Service issues
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-UIDL: pXh!!&Aod9\PJ!!C`n!!

Forwarding these issues about the notification service, received at 
experts@omg.org but more appropriate for issues.

Jon Siegel

senderName: Dora Potluri 
mailFrom: dora.2.potluri@mail.sprint.com
mailBody: 
CosNotification:  

I see the following features lacking in CosNotification spec.  What is
the process on having this raised as 
an issue, and if all agree add it to the spec in the later revisions.
Any info is appreciated.

2. Publishers are allowed to push events for the types they have not
offered using offer_change(). 
This can allow publishers to never advertise the event types they are
offerring.  For Example, as 
a consumer it can not tell what are the event types that will be
offered on the channel. 

Can we require publishers to always call offer_change() on the new
event types before pushing them to 
the event channel?  If this behavior breaks existing functionality,
then how about having push_xxx()
check to see if the event type is offered, if not add it to the
aggregate list?

Any info is appreciated. 

Thanks
Dora Potluri
Business & Technical Architecture
Sprint
Phone: 972-405-8005 (Work)
Email: dora.2.potluri@mail.sprint.com