X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=PPI%2FModule.hh;h=1c6aba1f28e7179f78841e031f1d22dae434eba3;hb=489be2bbd4d03259a17df14e4962a4524cd5b654;hp=03fa40f7d7417d675f731f436f9102240b85869c;hpb=a479735a65e334af538b895f182f8efd36a541c5;p=senf.git diff --git a/PPI/Module.hh b/PPI/Module.hh index 03fa40f..1c6aba1 100644 --- a/PPI/Module.hh +++ b/PPI/Module.hh @@ -1,6 +1,8 @@ -// Copyright (C) 2007 -// Fraunhofer Institut fuer offene Kommunikationssysteme (FOKUS) -// Kompetenzzentrum fuer Satelitenkommunikation (SatCom) +// $Id$ +// +// Copyright (C) 2007 +// Fraunhofer Institute for Open Communication Systems (FOKUS) +// Competence Center NETwork research (NET), St. Augustin, GERMANY // Stefan Bund // // This program is free software; you can redistribute it and/or modify @@ -104,8 +106,8 @@ namespace module { public: // Define connectors. Any number and type of connectors may be defined. Connectors // must be public since they need to be accessed to connect modules with each other. - senf::ppi::connector::PassiveInput input; - senf::ppi::connector::ActiveOutput output; + senf::ppi::connector::PassiveInput<> input; + senf::ppi::connector::ActiveOutput<> output; SomeModule(senf::FileHandle h) : handle ( h ), @@ -198,9 +200,9 @@ namespace module { The return value may be used to alter routing parameters like throttling parameters. - \param[in] source Data source, object which controls + \param[in] input Data source, object which controls incoming data (connector or event) - \param[in] target Data target, object which controls + \param[in] output Data target, object which controls outgoing data (connector or event) \returns Route instance describing this route \see \ref ppi_throttling @@ -227,10 +229,10 @@ namespace module { route(EventDescriptor & input, connector::OutputConnector & output); ///< Define flow information /**< Route from an event to a connector. Routing from an - event to a connector defeines the event as the - conceptual 'source' of the data. THis means, the event + event to a connector defines the event as the + conceptual 'source' of the data. This means, the event controls how packets are sent (Example: Routing from an - IOEVent to an output defines, that output data will be + IOEvent to an output defines, that output data will be generated whenever the event is signaled). This event routing allows to automatically