Re: [Pandora] Component::notify()

[uaca]

On Thu, Dec 05, 2002 at 06:20:05PM +0100, address@hidden wrote:
> 
> Hi (all?)
> 
> Please imagine the following stack:
> 
> @tcpscan [ $reject = false ];
> @demux [ $algo = "tcpcnx"] < @mycomponent >
[...]


Ok, I found tcpreorder's "force" parameter, but this component has diferent
needs:

demux will pass packets just initially wich tcpreorder will not want, 
but that's not the case of my example, remember:

> This will pass each TCP flow (both ways) to am instance of a "mycomponent"
> component
> 
> 
> What happens if @mycomponent just wants few packets?
> 
> 
> mycomponent when it's finished will return "true" from mycomponent::add()
> method so tcpcnx will destroy the branch with demux::notify(), that's fine
> 
> but next packets of the same TCP flow will come again and then another
> branch/instance of a "mycomponent" will be created, but remember:
> 
> we are no longer interested in this TCP flow!


regards

        Ulisses

                Debian GNU/Linux: a dream come true
-----------------------------------------------------------------------------
"Computers are useless. They can only give answers."            Pablo Picasso

--->    Visita http://www.valux.org/ para saber acerca de la    <---
--->    Asociación Valenciana de Usuarios de Linux              <---