- 
                            Key: CORBA26-52
- 
                            Legacy Issue Number: 3998
- 
                            Status: closed
- 
                            Source: Open Networks Engineering ( Jean-Christophe Dubois)
- 
                            Summary:As the CCM spec is not giving any mean (or very little) to fill in the 
 filterable body part, no services are provided for a component to set its
 event filters when sending or receiving events.This seems to be a very usefull service to me for application such as: - limiting the number of events emitted by a component based on a config
 parameter (like messages with priority > config value can go out, other are
 discarded. when the config value change at runtime the filter could also
 change.
- filtering events received from a notification channel.
 I agree that these 2 function could be achieve by user code in the component 
 but it means that unecessary events are passed between components and the
 netwok load and CPU load is higher than necessary.I guess the point I am trying to make is that using the notification service 
 without using filters and/or filterable body doesn't seem to make a lot of
 sense.What is the intend of the sepc on this issue? 
- limiting the number of events emitted by a component based on a config
- 
                            Reported: CORBA 2.4 — Wed, 25 Oct 2000 04:00 GMT
- 
                            Disposition: Resolved — CORBA 2.6.1
- 
                            Disposition Summary:See issue 3938. rejected 
- 
                            Updated: Fri, 6 Mar 2015 20:58 GMT