Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 39749 invoked by uid 500); 10 Jun 2002 14:13:11 -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 39738 invoked from network); 10 Jun 2002 14:13:11 -0000 Message-ID: <911C684A29ACD311921800508B7293BA0221DBC5@cnmail> From: Geoff Howard To: "'cocoon-dev@xml.apache.org'" Subject: RE: XInclude Transformer vs CInlude Transformer Date: Mon, 10 Jun 2002 10:00:50 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N IIRC the current XInclude transformer does not support caching. Geoff Howard > -----Original Message----- > From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net] > Sent: Sunday, June 09, 2002 2:32 PM > To: cocoon-dev@xml.apache.org > Subject: RE: XInclude Transformer vs CInlude Transformer > > > > From: Mattam [mailto:mattam@netcourrier.com] > > > > Ivelin Ivanov [Sun, 09 Jun 2002 11:22:07 -0500]: > > > > | > > | Two almost identical transformers are confusing me. > > | What is the difference between the two? > > | Should one be deprecated? > > | > > | I'd vote for the one which implements the W3C XInclude > spec closest. > > | Maybe it should take the best of the other one. > > | > > > > CInclude allows cocoon:/ protocol, and XInclude tends to be a strict > > implementation of the standard. Maybe keeping only XInclude while > allowing the > > cocoon:/ protocol (with a switch?) would be the better. > > That's not right; XInclude also works with cocoon: protocol, they both > use Cocoon's resolver. > > IIRC, the reason of CInclude existence is completely different: if you > remove CInclude, it will be more complicated to serve documents with > inclusions and with tags in xinclude namespace. Right now, this is not > an issue: create document with xinclude *and* cinclude tags, > process it > through cinclude, and xinclude will remain intact, no sweat. > > Vadim > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org