Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 47122 invoked from network); 29 Sep 2004 08:26:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 29 Sep 2004 08:26:22 -0000 Received: (qmail 60433 invoked by uid 500); 29 Sep 2004 08:26:18 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 60259 invoked by uid 500); 29 Sep 2004 08:26:16 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 60246 invoked by uid 99); 29 Sep 2004 08:26:16 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [84.96.21.10] (HELO mail.anyware-tech.com) (84.96.21.10) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 29 Sep 2004 01:26:15 -0700 Received: from [10.0.0.134] (unknown [10.0.0.134]) by mail.anyware-tech.com (Postfix) with ESMTP id 045EA5EE73 for ; Wed, 29 Sep 2004 10:26:11 +0200 (CEST) Message-ID: <415A71A3.6050401@apache.org> Date: Wed, 29 Sep 2004 10:26:11 +0200 From: Sylvain Wallez Organization: Anyware Technologies User-Agent: Mozilla Thunderbird 0.8 (Macintosh/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Interesting on Servlet References: <4159F358.10500@apache.org> In-Reply-To: <4159F358.10500@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Stefano Mazzocchi wrote: > Pier Fumagalli wrote: > >> http://www.mortbay.com/MB/log/gregw/?permalink=servletNG.html >> >> Pier > > > wow, what do you think it would take to create a CocoonServletNG? Cocoon could return a Source object which, AFAIU is not that far from Greg's idea of using the ContentHandler API. A FileSource (e.g. returned by a Reader) could then be memory-mapped by the container, and we may even think of a container-managed cache where Cocoon just computes the validity. Just some random thoughts... Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }