cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <>
Subject Re: [RT] Protocol based sources eliminates almost every generator [was Re: Showstoppers for 2.0 final was RE: [tale+rant] The 2.0 syndrome and [Vote]: Final Release Date]
Date Mon, 26 Nov 2001 15:41:17 GMT
Giacomo Pati wrote:

> Quoting Berin Loritsch <>:
>>I *do* have a problem with making it the end all and be all of creating
>>XML.  The Generator's responsibility is to convert an XML based Source
>>to SAX events.  The Source is the abstraction of where the Generator
>>retrieves the information to convert to XML.
> So, you think the cocoon:/ protocol is nothing to be implemented as a Source 
> (becaus it produces a SAX stream itself)?

The "cocoon:" protocol has always been an exception--as it is the *only* way of
including information that is generated from another part of the sitemap.  We
all know that converting the SAX stream to an IO stream and back again is
inneficient at best.

This is a hard balance to make, because conceptually the "cocoon:" protocol
represents a Source that is a Pipeline ("PipelineSource"?).  This is a very
powerful tool if used correctly--and a performance sink if used incorrectly.

*All* Source objects should work _with_ the cache, so that speed-ups are as quick
as they possibly could be.  This way, the XInclude and CInclude transformers can
easily take advantage of the cache.


"Those who would trade liberty for
  temporary security deserve neither"
                 - Benjamin Franklin

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

View raw message