I'm just thinking about a possible use for a Carousel. Suppose I have a pipeline of three components, A, B & C. I'd like B to be able to change dynamically, so make it a Carousel that loads one of several possible children. Those children are threaded components.
As I understand it, when I want to change component B, the Carousel tells its child to terminate, then waits for it to do so, then unlinks its inboxes and outboxes, then creates the new child. If the child is a threaded component, its inbox is a queue which may still have messages in it when the child terminates. Those messages are then lost and won't find their way through the pipeline. Would it be better if the carousel cut off the child's inboxes before telling it to terminate? The child could then process anything remaining in its inbox queue before terminating. We'd still need a way to suspend component A while switching to the new component B though. Ideally no messages leaving A would be lost, all would find their way to C via one or other of B's children. -- Jim Easterbrook Senior Research Engineer BBC Research & Development South Lab BBC Centre House 56 Wood Lane London W12 7SB Phone: +44 303 040 9705 Mobile: +44 7590 307002 FAX: +44 20 8811 8815 -- You received this message because you are subscribed to the Google Groups "kamaelia" group. To post to this group, send email to kamae...@googlegroups.com. To unsubscribe from this group, send email to kamaelia+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/kamaelia?hl=en.
