|
ADTF
3.18.2
|
The main task of a filter is to interconnect runnable components and processing data.
The Filter basics are implemented in the Filter. It defines a filter default implementation.
The ADTF Filter SDK defines the internal architecture of the filter implementation and will give you the possibility to embed your own functionality into ADTF. Usually you do not implement a filter but a Legacy Trigger Function as running component of a filter.
The provided Filter implementation cFilter supports following behaviour to execute your Legacy Trigger Function.
Following Triggers are supported by this filter:
The Data In Trigger is configurable by the cFilter::ConfigureDataInTrigger. It will create a simple internal Trigger Pipe between IInPin and IRunner.
The Data Out Trigger is configurable by the cFilter::ConfigureDataOutTrigger. It will create a simple internal Trigger Pipe between IRunner and IOutPin.
The Timer Trigger is configurable by the function cFilter::ConfigureTimerTrigger. It will not create any internal pipe. This information of your Filter is used to add a Timer Runner to the ADTF Graph XML Schema file. The configuration is added to the Plugin Description Concept.
The Thread Trigger is configurable by the function cFilter::ConfigureThreadTrigger. It will not create any internal pipe. This information of your Filter is used to add a Thread Runner to the ADTF Graph XML Schema file. The configuration is added to the Plugin Description Concept.
The Default Trigger information will be used to create the Plugin Description Concept by the ADTF Plugin Description Generator. This functionality was implemented for your convenience to reduce the clicki-configuration time.
Programmers can also use adtf::filter::testing::ant::create_default_runners within its testing environment. The implementation of the Filter Graph (adtf::streaming::ant::cFilterGraph) will NOT automatically add Thread and Timer objects to the Filter Graph instance.