cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From giacomo <>
Subject Re: [C2] Internal requests and Readers
Date Fri, 09 Nov 2001 20:04:05 GMT
On Fri, 9 Nov 2001, Joerg Henne wrote:

> Hi,
> today I had to learn the hard way, that cocoon currently does not seem to
> support internal requests (using the cocoon:-protocol) that will be served by
> readers.

What was your reason to feed an cocoon:/ URL to a reader??


> This is due to the fact that the SitemapSource's refresh method
> bypasses the StreamPipeline when executing an internal request and asks the
> EventPipeline to stream the XML directly to itself or it's consumer.
> Well, this is obvoiusly the correct and most efficient thing to do for
> pipelines that generate XML. However, for pipelines consisting of readers,
> this will fail. Architecture-wise it would, in my opinion, be desirable to
> allow any combination of XML or stream generating pipeline and XML or stream
> generating consumer. In order to do so, it would be necessary to what kind of
> data the pipeline will generate and then employ a "stream pump" or an XML
> parser to feed the consumer. This is further complicated by the fact that
> plumbing an OutputStream to an InputStream either requires a separate Thread
> or the Buffering of the whole stream.
> As I'm not too familiar with this part of cocoon I probably have missed
> somthing. Has someone already spent some more brain-cycles on this Problem? Is
> it really necessary to jump through these hoops? Do we want it?
> TGIFE :-)
> Joerg Henne
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:

To unsubscribe, e-mail:
For additional commands, email:

View raw message