Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 43906 invoked by uid 500); 9 Apr 2003 20:40:21 -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 43892 invoked from network); 9 Apr 2003 20:40:20 -0000 Received: from gate1.stjude.org (192.55.208.11) by daedalus.apache.org with SMTP; 9 Apr 2003 20:40:20 -0000 Received: by gate1.stjude.org; (8.9.3/1.3/10May95) id PAA881160; Wed, 9 Apr 2003 15:40:24 -0500 (CDT) Received: from somewhere by smtpxd Message-ID: <601F6322AD71D5118D6C0003472515290660D1F5@sjmemexc1.stjude.org> From: "Hunsberger, Peter" To: "'cocoon-dev@xml.apache.org'" Subject: RE: [RT] the quest for the perfect template language Date: Wed, 9 Apr 2003 15:40:15 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Stefano Mazzocchi asked: > So, this list seems full of XSLT lovers, then get your brain cells > working: how do we sort the performance issues of document()? > I realize this isn't what you're asking for, but the following came up on xml-dev the other day: http://www-106.ibm.com/developerworks/xml/library/x-injava/index.html It's a comparison of the performance of various parsers. Interestingly enough (when considered with some of the other discussion in this thread) a pull model parser (XPP) comes out on top most of the time. Isn't the document issue really attacked by treating it exactly as any other *internal* Cocoon URI reference (via the URI resolver hook)?