[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Microsoft's vision of data and the role of XML in that con

• To: <xml-dev@l...>
• Subject: Re: Microsoft's vision of data and the role of XML in that context
• From: Arjun Ray <aray@n...>
• Date: Wed, 18 Sep 2002 22:23:38 +0000
• In-reply-to: <4F4182C71C1FDD4BA0937A7EB7B8B4C10662CCD9@r...>
• References: <4F4182C71C1FDD4BA0937A7EB7B8B4C10662CCD9@r...>

"Joshua Allen" <joshuaa@m...> 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"?  

• Follow-Ups:
  • RE: Microsoft's vision of data and the role of XML in that context
    • From: "Aaron Skonnard" <aarons@d...>

• References:
  • RE: Microsoft's vision of data and the role of XML in that context
    • From: "Joshua Allen" <joshuaa@m...>

• Prev by Date: RE: Microsoft's vision of data and the role of XML in that context
• Next by Date: RE: strange feeling
• Previous by thread: RE: Microsoft's vision of data and the role of XML in that context
• Next by thread: RE: Microsoft's vision of data and the role of XML in that context
• Index(es):
  • Date
  • Thread