Todd --
For the UseXMLFilters example, of course, either way will work just
fine. The problem arises when one of the filters wants to override the
parse method. Perhaps, it only wants to letter certain URLs through or
check some special security or something. In your second scenario, the
parse
Hey, nice picture (the first one). We should use it in our docs.
Yes, you're correct in your analysis.
> why have the
> Xml input doc be 'forwarded' from the end of the pipe to the beginning,
> to be read? Why not design the pipeline such as
Well, first of all, it's not our design, it's how
