(msg) If we have some FUs which might not be used by other FUs for DataTransmission, does it make sense to have special FUs for this? This FU is a good example it will never be used by any other FU for data transmission, or?
(msg) If we have some FUs which might not be used by other FUs for DataTransmission, does it make sense to have special FUs for this? This FU is a good example it will never be used by any other FU for data transmission, or?
(msg) Rename this method into allocatePhysicalResource and add a method freePhysicalResource. This way the PhysicalResources can be freed if they are not needed by anyone any longer.
msg@comnets.rwth-aachen.de 23.10.2007: blockLenght, CWL and all the other stuff should be "int" instead of "unsigned int" to be able to say assure(blockLength > 0, ...). This is useless with "unsigned int" since this is always true.
Marc Schinnenburg: If the element T is derived from SingleFastListEnabler, it would be nice to generate a compile-time error, since copying the list is not allowed in this case.
dbn: This was introduced to handle LogEval in some way. LogEvals flush their contents completely to disk and thus cannot be const. We should think of a generic way to handle both possibilities behind a common interface.
pab, 2007-02-12: cloning the flowseparator currently results in multiple flowseparators sharing the same notFoundStrategy Object and the same KeyBuilder Object
(msg, ksw, swen) This should be removed. The problem here is that the Delayed interface should have two methods to be called in advance and after getSomethingToSend(), respectively.
currently, Producer creates Compounds with a fresh Command. But it would be nicer to have policies for the creation of Compounds. Another useful creational policy could follow the prototype pattern: Give the producer a PDU to make copies of... Or maybe something even smarter?
<msg@comnets.rwth-aachen.de> In the future, this function will be able to return a list of functors which contain member functions pointers. These functors can be called by a Component 'Dependency Resolver' to, well, resolve all dependencies.