• To: xml-dev@l...
• Subject: Re: Microsoft's vision of data and the role of XML in that context
• From: Joe English <jenglish@f...>
• Date: Wed, 18 Sep 2002 15:00:56 -0700
• In-reply-to: <4F4182C71C1FDD4BA0937A7EB7B8B4C10662CCD9@r...>
• References: <4F4182C71C1FDD4BA0937A7EB7B8B4C10662CCD9@r...>

Joshua Allen 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.  "Pull to read, push to write"
> makes it easy for developers to write components which automatically
> "just works" in a pipelined environment.

Could you elaborate on this?  I'm confused.

If every component follows this model, how do you plug
two of them together?  That is, how can the output of
FOO be the input of BAR if FOO wants to push and BAR
wants to pull?  Threads?


--Joe English

  jenglish@f...

• Follow-Ups:
  • RE: Microsoft's vision of data and the role of XML in that context
    • From: Bill de hÓra <bill.dehora@p...>
  • RE: Microsoft's vision of data and the role of XML in that context
    • From: "Aaron Skonnard" <aarons@d...>
  • RE: Microsoft's vision of data and the role of XML in that context
    • From: "Steven Livingstone" <s.livingstone@b...>

• 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 thatcontext
• Next by Date: RE: Microsoft's vision of data and the role of XML in that context
• Previous by thread: Re: Microsoft's vision of data and the role of XML inthat context
• Next by thread: RE: Microsoft's vision of data and the role of XML in that context
• Index(es):
  • Date
  • Thread