Harald, Great question. Previously Click didn't really support this use case; it implicitly assumed that a Notifier belonged to a whole element. But I've added a new function, Element::port_cast(), that the notifier code uses to potentially differentiate notifiers by port. Please update and see the code.
Eddie Harald Schiöberg wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > How to handle the EMPTY_NOTIFIER correctly if one has multiple pull > ports? AFAIK there is exactly one Notifer that can be returned by the > cast function as Notifier::EMPTY_NOTIFIER > > What is the expected behavior of a multi-pull-port element that has > packets in only some of the ports? > > > thanks > Harald > > - -- > Harald Schiöberg > Technische Universität Berlin | T-Laboratories | FG INET > www: http://www.net.t-labs.tu-berlin.de > Phone: +49-(0)30-8353-58476 | Fax: +49-(0)391 534 783 47 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFI24LGy8wrZ9OvkU0RAjJHAJoDh08mnGpL+uvBBvhhxYVboZBBHQCgsm5Q > z+oqqxLP9c5MfPuf44JQngY= > =UoQ6 > -----END PGP SIGNATURE----- > > _______________________________________________ > click mailing list > click@amsterdam.lcs.mit.edu > https://amsterdam.lcs.mit.edu/mailman/listinfo/click _______________________________________________ click mailing list click@amsterdam.lcs.mit.edu https://amsterdam.lcs.mit.edu/mailman/listinfo/click
