Bug 445 - Implement an example with user-supplied event headers.
Summary: Implement an example with user-supplied event headers.
Status: ASSIGNED
Alias: None
Product: TAO
Classification: Unclassified
Component: Real-Time Event Service (show other bugs)
Version: 1.0.13
Hardware: All All
: P5 enhancement
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks:
 
Reported: 2000-02-18 23:15 CST by Carlos O'Ryan
Modified: 2003-04-13 19:18 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 2000-02-18 23:15:35 CST 
It is possible to modify the event header to include some other information that
the user wants to filter on.
This requires a custom Filter_Builder that can create a ad-hoc EC_Filter based
on the application specific information in the Event Header.  It may also be
convenient to provide an application specific ConsumerQOS and SupplierQOS
factories.
Unfortunately this requires patching the RtecEventComm.idl file, a more
disturbing prospect.  Ideally we would like to have a framework to provide
developers with "incomplete Event Services", the framework would be used to
implement the custom event channel, using a completely different IDL interface.
This bug report is just a reminder of this idea, maybe we could implement an
example of such modifications to the EC or (if we are lucky) the framework
hinted at above.
Comment 1 Carlos O'Ryan 2000-02-18 23:17:59 CST 
I'm accepting the "bugs", more like wish list entries or reminders of possible
work actually.
Comment 2 Carlos O'Ryan 2003-04-02 12:26:21 CST 
I will never have time to work on these bugs.  Returning them to the TAO support
pool.
Comment 3 Nanbor Wang 2003-04-13 19:18:13 CDT 
Accept for tao-support