-// 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 <g0dil@berlios.de>
//
// This program is free software; you can redistribute it and/or modify
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 ),
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
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
generated whenever the event is signaled).