On 22 Apr 2004, at 21:04, Matt Sergeant wrote:
On 22 Apr 2004, at 17:08, Kip Hampton wrote:
Matt Sergeant wrote:
We need to come to a decision on this - whether to fundamentally change our pipeline model in AxKit-2.0.
I think the only sane answer to "do we do implement a pull or a push model for the core pipelines?" is "Yes!". What I mean is: why don't we make the pipeline just YA swappable component rather than hard-coding one model or the other?
Thoughta?
My thoughta is this might be needless complexity (?). Though I really do need to sit down with the code and play some. Would making the pipeline swappable make it incompatible with the ConfigReader (or rather, make it tied to the ConfigReader)?
Well the config reader would obviously have to support the option in the same way it supports
other Ax* directives... But I don't think it adds needless complexity. Theoretically it should
make axkit more powerful, by allowing people to more interesting stuff than just a straight pipeline.
After all, almost everything else is plugable, including the config reader, so why not the pipeline?
Mike.
