TAO_EC_Null_Filter Class Reference

A null filter. More...

#include <EC_Filter.h>

Inheritance diagram for TAO_EC_Null_Filter:

Collaboration diagram for TAO_EC_Null_Filter:

List of all members.

Public Member Functions
	TAO_EC_Null_Filter (void)
	Constructor.
virtual int	filter (const RtecEventComm::EventSet &event, TAO_EC_QOS_Info &qos_info)
virtual int	filter_nocopy (RtecEventComm::EventSet &event, TAO_EC_QOS_Info &qos_info)
virtual void	push (const RtecEventComm::EventSet &event, TAO_EC_QOS_Info &qos_info)
virtual void	push_nocopy (RtecEventComm::EventSet &event, TAO_EC_QOS_Info &qos_info)
virtual void	clear (void)
virtual CORBA::ULong	max_event_size (void) const
	Returns the maximum size of the events pushed by this filter.
virtual int	can_match (const RtecEventComm::EventHeader &header) const
virtual int	add_dependencies (const RtecEventComm::EventHeader &header, const TAO_EC_QOS_Info &qos_info)

---

Detailed Description

A null filter.

This filter accepts any kind of event, it is useful for the implementation: a) Consumers that accept all events b) Consumers that trust the filtering done at the Supplier layer. c) Event Channels that don't do filtering (such as CosEC backends)

---

Constructor & Destructor Documentation

TAO_EC_Null_Filter::TAO_EC_Null_Filter

(

void

)

Constructor.

---

Member Function Documentation

int TAO_EC_Null_Filter::add_dependencies	(	const RtecEventComm::EventHeader &	header,
		const TAO_EC_QOS_Info &	qos_info
	)		[virtual]

This is used for computing the scheduling dependencies:

Leaf filters check if the header could be matched, similar to the can_match() method; if it does they return 1, and 0 otherwise. Intermediate nodes always return 0.

This is used to build precise dependencies between the suppliers and the leaf of the filters that accept that event. Notice that only the nodes doing scheduling recurse through the list, so in configurations that do no require scheduling the recursion stops fairly soon.

Implements TAO_EC_Filter.

int TAO_EC_Null_Filter::can_match

(

const RtecEventComm::EventHeader &

header

)

const [virtual]

Returns 0 if an event with that header could never be accepted. This can used by the suppliers to filter out consumers that couldn't possibly be interested in their events. The rt_info and

Implements TAO_EC_Filter.

void TAO_EC_Null_Filter::clear

(

void

)

[virtual]

Clear any saved state, must reset and assume no events have been received.

Implements TAO_EC_Filter.

int TAO_EC_Null_Filter::filter	(	const RtecEventComm::EventSet &	event,
		TAO_EC_QOS_Info &	qos_info
	)		[virtual]

Filter this event, returns 1 if the event is accepted, 0 otherwise. Notice that there are two versions of the method, if the event is not const then filter can take ownership of the event.

Attention:

There seems to be a disparity in interfaces: Supplier always push event sets of size 1 to the EC_ProxyPushSupplier, and EC_Filters do not implement handling of sets of more than 1 event. Then, why is this not enforced by the interface by having EC_ProxyPushSupplier take an event rather than a set?

Implements TAO_EC_Filter.

int TAO_EC_Null_Filter::filter_nocopy	(	RtecEventComm::EventSet &	event,
		TAO_EC_QOS_Info &	qos_info
	)		[virtual]

Implements TAO_EC_Filter.

CORBA::ULong TAO_EC_Null_Filter::max_event_size

(

void

)

const [virtual]

Returns the maximum size of the events pushed by this filter.

Implements TAO_EC_Filter.

void TAO_EC_Null_Filter::push	(	const RtecEventComm::EventSet &	event,
		TAO_EC_QOS_Info &	qos_info
	)		[virtual]

This is called by the children when they accept an event and which to pass it up. Notice that there are two versions of the method, if the event is not const then filter can take ownership of the event.

Implements TAO_EC_Filter.

void TAO_EC_Null_Filter::push_nocopy	(	RtecEventComm::EventSet &	event,
		TAO_EC_QOS_Info &	qos_info
	)		[virtual]

Implements TAO_EC_Filter.

---

The documentation for this class was generated from the following files:

• EC_Filter.h
• EC_Filter.cpp
• EC_Filter.inl