[
Lists Home |
Date Index |
Thread Index
]
I don't quite get why it could possibly be any easier using SAX - you
can still use the same interface - it's then up to you how you implement
within the pipeline itself. It is trivial to plug them together as
follows:
ms contains file stream..
fm.runPipe1(ms);
fm.runPipe2(ms);
fm.runPipeN(ms);
fm.runFilters();
XmlReader rdr = new XmlReader(ms);....
I have implemented this with no probs at all with the same interface - a
stream containing the Xml doc - and process the doc as a pipeline using
the XmlReader and XmlWriter.
Unless of course you mean something different :)
Steven.
==========================================================
Steven Livingstone BSc (hons), PgDip ITS [s.livingstone@btinternet.com]
.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"
==========================================================
-----Original Message-----
From: Aaron Skonnard [mailto:aarons@develop.com]
Sent: 19 September 2002 01:06
To: xml-dev@lists.xml.org
Subject: RE: [xml-dev] Microsoft's vision of data and the role of XML in
that context
> 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?
I'm confused too. IMO, XML processing pipelines are much easier to
implement in SAX that with the .NET APIs (this is actually the
1-out-of-10 scenario I alluded to in my previous post). Since the same
interface, ContentHandler, was used for both reading and writing, it was
trivial to plug them together. This is not the case in .NET. Do you mean
a pipeline of readers or a pipeline of writers, but not where one feeds
into the other?
-aaron
......................................................
. Aaron Skonnard, DevelopMentor (http://skonnard.com).
. Essential XML Quick Reference available online! .
. Download PDFs: http://www.develop.com/books .
......................................................
-----------------------------------------------------------------
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
manager: <http://lists.xml.org/ob/adm.pl>
|
