Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 95922 invoked by uid 500); 26 Nov 2001 15:39:35 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 95903 invoked from network); 26 Nov 2001 15:39:34 -0000 Message-ID: <3C02629D.3010200@apache.org> Date: Mon, 26 Nov 2001 10:41:17 -0500 From: Berin Loritsch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.6) Gecko/20011120 X-Accept-Language: en-us MIME-Version: 1.0 To: cocoon-dev@xml.apache.org 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] References: <3C023D82.7000900@rabellino.it> <1006780725.3c024135241ce@mail.otego.com> <3C0247B1.4090803@cbim.it> <3C0251DE.90003@apache.org> <1006786271.3c0256df798c2@mail.otego.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org