Bug 32

Summary:	Implement trivial consumer filter but with correct event matching
Product:	TAO	Reporter:	Carlos O'Ryan <coryan>
Component:	Real-Time Event Service	Assignee:	DOC Center Support List (internal) <tao-support>
Status:	ASSIGNED ---
Severity:	enhancement
Priority:	P3
Version:	0.4
Hardware:	All
OS:	All

Description Carlos O'Ryan 1999-07-07 23:55:37 CDT

The null consumer filters match any events, so they effectively ignore the
consumer QoS requirements.  For applications that only have disjunctions it
could be more efficient to perform all the filtering on the supplier side, i.e.
exploit the information about the supplier publications to build the exact set
of consumers interested in a particular event type/source pair.
This will require a consumer filtering strategy that correctly implements the
can_match() method, but whose filter() method is trivial.

Comment 1 Carlos O'Ryan 1999-07-10 20:20:59 CDT

Another enhancement for the real-time event service, mine too.

Comment 2 Carlos O'Ryan 2000-02-19 21:41:59 CST

Update the priority, it is interesting, but not a pressing problem.

Comment 3 Carlos O'Ryan 2003-04-02 12:26:29 CST

I will never have time to work on these bugs.  Returning them to the TAO support
pool.

Comment 4 Nanbor Wang 2003-04-13 19:13:18 CDT

Accepting for tao-support