Lists Home |
Date Index |
"Joshua Allen" <email@example.com> wrote:
| The forward-only "pull model" is quite important because many of our
| low-level scenarios involve pipelined processing of XML, where
| performance and working set are critical.
Well, I'm usually going backwards when I pull :-)
Is "forward-only" in contrast to "forward-and-backward""? If so, why
would stuff have to flow backward?
| "Pull to read, push to write"
Is this a profundity or a truism?
| makes it easy for developers to write components which automatically
| "just works" in a pipelined environment.
Sounds like there's an I/O layer between each component, otherwise I can't
make sense of it.
Isn't the problem with "pulling", as opposed to "being pushed", that the
puller now would have to farm out work based on examining the input? No
polymorphic dispatch because the switch statement block is "small"?