[Click] Multiple pull ports: EMPTY_NOTIFIER ?

[Harald Schiöberg]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Eddie,

Sorry for the slightly late response:
Works like a charm .... as always.

Thanks a lot
	Harald

Eddie Kohler wrote:
> 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:
> 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
> 
>>
_______________________________________________
click mailing list
click at amsterdam.lcs.mit.edu
https://amsterdam.lcs.mit.edu/mailman/listinfo/click

- --
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

iD8DBQFL2xSsy8wrZ9OvkU0RArXDAJ9L8oja084QPi+ucaVtcehPVAReWgCfenbW
wneNmnHXNkfI+HlDzegN5U0=
=PHXP
-----END PGP SIGNATURE-----