Lists Home |
Date Index |
I did some work on Xml pipes recently and it is very easy ( and very
In my case, I used an XmlReader (pull Xml) and XmlWriter (push Xml)
which are both abstract classes and a single Stream (byte stream) and
that can be modified by each pipe.
You can thread it too if you want, but at the basic level you have a
single stream which can be modified by each pipe and passed into the
I have to say I love it and it's one of the coolest things I've done
with Xml in .Net - and it was pretty easy as well :)
Steven Livingstone BSc (hons), PgDip ITS [firstname.lastname@example.org]
.Net & Xml Consultant
Change your business at http://www.deltabis.net
Grow your business at http://www.venturetogether.com
Change European Football at http://www.theatlanticleague.com
*** Author of "Application Development with MSXML 4.0"
*** Coming Soon to a developer near you...
"Beg VB.NET XML:Essential XML Skills for VB.NET Programmers"
"Beg C# XML:Essential XML Skills for C# Programmers"
From: Joe English [mailto:email@example.com]
Sent: 18 September 2002 23:01
Subject: Re: [xml-dev] Microsoft's vision of data and the role of XML in
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?
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription