• To: xml-dev@l...
• Subject: Re: XML Pipeline
• From: Ronald Bourret <rpbourret@r...>
• Date: Sat, 04 Dec 2004 20:57:05 -0800
• In-reply-to: <1102141005.41b1564d2e661@65.39.203.11>
• References: <009801c4d941$ad985600$6501a8c0@dell8100> <20041203201954.25440.qmail@w...> <e3a5cb2c0412031223645b7858@m...> <41B14D45.8000902@r...> <1102141005.41b1564d2e661@65.39.203.11>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)

I'm not sure why a pipeline wouldn't modify the contents. Isn't that the 
point of pipes? For example, UNIX pipes are used to pass a character 
stream from program A to program B, which modifies that stream and 
passes it to program C, and so on. An XML pipeline, it seems, would do 
the same thing, with the data stored in a document and the programs 
being XML aware.

-- Ron

david.lyon@c... wrote:
> ok, I know nothing...
> 
> but it doesn't sound like an xml pipeline to me..
> 
> one would normally think that the pipes wouldn't
> be modifying the contents. You wouldn't normally
> want that in a pipeline.
> 
> It might be a relay, or a daisy-chain, but it
> doesn't really sound like what you need is
> a pipeline...

• Follow-Ups:
  • Re: XML Pipeline vs an XML Grid
    • From: david.lyon@c...

• References:
  • XML Pipeline
    • From: "Stephen E. Beller" <sbeller@n...>
  • Re: XML Pipeline
    • From: Christopher Milton <cmiltonperl@y...>
  • Re: XML Pipeline
    • From: Michael Champion <michaelc.champion@g...>
  • Re: XML Pipeline
    • From: Ronald Bourret <rpbourret@r...>
  • Re: XML Pipeline
    • From: david.lyon@c...

• Prev by Date: Re: Data streams
• Next by Date: Re: RE: Incremental transformations with Xalan and performance issues?
• Previous by thread: Re: XML Pipeline
• Next by thread: Re: XML Pipeline vs an XML Grid
• Index(es):
  • Date
  • Thread