Bug 29 - Implement a example that shows how to use filtering with the CosEC
Summary: Implement a example that shows how to use filtering with the CosEC
Status: NEW
Alias: None
Product: TAO
Classification: Unclassified
Component: CosEvent Service (show other bugs)
Version: 0.4
Hardware: All All
: P5 trivial
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks:
 
Reported: 1999-07-07 23:46 CDT by Carlos O'Ryan
Modified: 2007-05-01 06:45 CDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos O'Ryan 1999-07-07 23:46:10 CDT 
The CosEC uses the real-time event service as its back-end, it can exploit this
service to implement filtering between multiple CosEC.
The current example is hard to read and the output is not clear, it should
be improved to clearly highlight this feature.
Comment 1 Pradeep Gore 1999-07-16 09:36:59 CDT 
IMHO both the CosEvent examples should be revamped this way -
1. write a PushConsumer_ServantBase and PushSupplier_ServantBase. .This way it
will be easier for application developers to write suppliers/consumers because
that will handle all the common code like getting the proxypushconsumer,
and disconnecting when done etc.

2.I only managed to put the base class for the CosEC in the CosEvent_Utilities
and thats used by the EventService and the factory. i have to change the
CosEC_Basic example to use that as well.

3.CosEC_Multiple: If we use the servant base classes for this example
then it will thin down the code a lot. the same will happen for
CosEC_Basic too.

4.Additionally i have to debug the run_test.pl files for this example.
Comment 2 Johnny Willemsen 2007-05-01 06:45:40 CDT 
to pool