[Clam-devel] NaiveFlowControl: Missing case

[David García Garzón]

Some more use case:

 * Branch saturation
      Example: A branch ending in a monitor which has a lower Do granularity 
(it needs more Do's to process the same) than the branch ending on the Sink.
FlowControl Do ends as soon as the Sink is executed and this happens on less 
loops than the monitor branch. So data in monitor branch don't get consumed 
and at last writting on the buffer to get into the branch is not possible.

Any other one?


On Dimarts 27 Febrer 2007, David García Garzón wrote:
> Just to remember it for tomorrow. The current NaiveFlowControl we
> implemented today does not support the following cases:
>
>  * Filter with bigger size + a ever runable processing
>      Ever runnable processings can be a set of processing not connected to
> callback interfaces (FileIn+Oscillator) or a port less processing such
> control senders. The filter with bigger size makes some iterations end
> without filling the sink but as always there are some processing to run,
> Do() will run with no end.
>
>  * Network without a sink
>       Like analysis networks or fileOut recording. As the finalization
> condition is right now not having any sink. The flow control will just exit
> without running any other processing than sources.
>
> David.
>
>
>
>
>
> _______________________________________________
> Clam-devel mailing list
> Clam-devel at llistes.projectes.lafarga.org
> https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel



-- 
David García Garzón
(Work) dgarcia at iua dot upf anotherdot es
(Home) vokimon at telefonica adot net
http://www.iua.upf.edu/~dgarcia
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.clam-project.org/pipermail/clam-devel-clam-project.org/attachments/20070228/cc8851dd/attachment.sig>