Thanks.. I think that for the level of usage I envision, the flexiblity of
[chain] (and relative maturity) solves the problem, even though [pipeline]
may in a larger sense be more appropriate for my use case.
My usecase, processing data, seems to fit into exactly what [pipeline] does.
In fact, I
> I was also looking at [pipeline] in sandbox, and was trying to grok the
> difference. What it seemed to boil down to is that in a pipeline you go
> from A -> Z without ever stopping. But, in [chain] you may go from A ->
Z,
> but if certain conditions occur, you may stop midway at J, correct?
I
Hi all,
Just checking out [chain], was thinking of replacing my own CoR
implementation. The one thing that I have, that chain doesnt, is a visitor
object. Now, I may be mixing up my GoF patterns here, but what I have are a
series of steps that are ordered. I have a visitor who goes from one to
