Objects of classes which implement this specialized InConnector interface provide the ability to receive events in pull-style manner by means of one transport mechanism. More...

#include <InPullConnector.h>

Inheritance diagram for rsb::transport::InPullConnector:

Collaboration diagram for rsb::transport::InPullConnector:

Public Types
typedef boost::shared_ptr < InPullConnector >	Ptr
Public Types inherited from rsb::transport::InConnector
typedef boost::shared_ptr < InConnector >	Ptr

Public Member Functions
virtual	~InPullConnector ()
virtual EventPtr	raiseEvent (bool block)=0
Public Member Functions inherited from rsb::transport::InConnector
virtual	~InConnector ()
Public Member Functions inherited from rsb::transport::Connector
virtual	~Connector ()
virtual void	setScope (const Scope &scope)=0
	Sets the scope this connector will send/receive events to/from.
virtual void	activate ()=0
	Activates the connector.
virtual void	deactivate ()=0
virtual void	setQualityOfServiceSpecs (const QualityOfServiceSpec &specs)=0
	Requests new QoS settings for publishing events.
Public Member Functions inherited from rsb::filter::FilterObserver
	FilterObserver ()
virtual	~FilterObserver ()
virtual void	notify (Filter *filter, const FilterAction::Types &at)
virtual void	notify (ScopeFilter *filter, const FilterAction::Types &at)

Detailed Description

Objects of classes which implement this specialized InConnector interface provide the ability to receive events in pull-style manner by means of one transport mechanism.

In general, and especially when used in a constellation with one receiving participant and a single InPullConnector, the pull-style data-flow can be much more efficient than the push-style data-flow provided by InPushConnector.