On 10/06/2009 16:11, Michael Sparks wrote: > > Which links the output of D into the input of A. (A can still accept data > from > the outside world). In a way, this is potentially similar if you could do > something like: > > Pipeline( > A, > B, > C, > D, > circular = OnlySignals, > ).run()
This is the sort of thing I've been constructing using Graphline. The interesting question is what happens when that pipeline is used as a component in another pipeline. D's signal outbox needs to be connected both to A's control inbox and to the next component's control inbox. The outer pipeline would also need to have the "circular = OnlySignals" option. This is the sort of thing I meant by "play nicely with". Considering UNIX pipes (which is what I'm familiar with) any process can shut down the pipeline by exiting. The upstream processes terminate when they try to write and get a SIGPIPE. The downstream processes will terminate when they find their stdin has reached eof. Kamaelia doesn't seem to have any analogous behaviour. > You may also want to be aware of these experimental additions to Graphline, > Pipeline & Carousel by Matt a while back: > > http://www.kamaelia.org/Components/pydoc/Kamaelia.Experimental.Chassis I'll have a look later. -- Jim Easterbrook BBC Future Media & Technology http://www.bbc.co.uk/rd/ *** All opinions are mine and might not be shared by the BBC *** --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "kamaelia" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/kamaelia?hl=en -~----------~----~----~----~------~----~------~--~---
