From dev-return-86003-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Sat Apr 01 19:28:53 2006 Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 3857 invoked from network); 1 Apr 2006 19:28:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Apr 2006 19:28:52 -0000 Received: (qmail 12844 invoked by uid 500); 1 Apr 2006 19:28:51 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 12805 invoked by uid 500); 1 Apr 2006 19:28:50 -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 List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 12794 invoked by uid 99); 1 Apr 2006 19:28:50 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Apr 2006 11:28:50 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [66.111.4.25] (HELO out1.smtp.messagingengine.com) (66.111.4.25) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Apr 2006 11:28:49 -0800 Received: from frontend2.internal (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 75242D44A2D for ; Sat, 1 Apr 2006 14:28:27 -0500 (EST) Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend2.internal (MEProxy); Sat, 01 Apr 2006 14:28:25 -0500 X-Sasl-enc: BoPpjsnW2OqYBTcGcoi8NY9k2MFDO6aUuRUGOdVtACVM 1143919704 Received: from [10.0.0.3] (host-87-74-127-123.bulldogdsl.com [87.74.127.123]) by www.fastmail.fm (Postfix) with ESMTP id B562C7E4 for ; Sat, 1 Apr 2006 14:28:24 -0500 (EST) Message-ID: <442ED45A.2020509@odoko.co.uk> Date: Sat, 01 Apr 2006 20:28:26 +0100 From: Upayavira Organization: Odoko Ltd User-Agent: Thunderbird 1.5 (X11/20060309) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: A new CLI (was Re: [RT] The environment abstraction, part II) References: <43D7F616.5060909@nada.kth.se> <43DBBC6E.20401@apache.org> <43DD395F.5010009@nada.kth.se> <43DE48E2.6000707@apache.org> <43DE930F.50405@nada.kth.se> <43DFBDE2.5020508@apache.org> <43E1E786.5040008@nada.kth.se> <20060329063931.GB19361@igg.indexgeo.com.au> <442A343A.1090206@apache.org> <20060331033201.GA13559@igg.indexgeo.com.au> <442D8462.6070103@odoko.co.uk> <442E2C2B.705@apache.org> In-Reply-To: <442E2C2B.705@apache.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Carsten Ziegeler wrote: > Upayavira wrote: >> David Crossley wrote: >>> Carsten Ziegeler wrote: >>>> I can't speak for Daniel, but my idea/suggestion was to forget about the >>>> different environments and let Cocoon always run in a servlet container. >>>> The CLI would then be kind of a http client which starts up jetty and >>>> then generates the site using http requests. This would simplify some >>>> things in Cocoon, the question is if this would make the life of Forrest >>>> too hard? >>> Thanks to you all for the followup. I don't have a >>> ready answer yet. Will make sure that the other >>> Forrest people are aware. >> In the end, it doesn't really matter that much, and will be up to >> whoever volunteers to implement the new CLI. > > It depends a little bit on how we see things. My opinion :) is to remove > the environment > abstraction completly and simply use the servlet environment while > others might think that we should only base our environment abstraction > on the servlet api but allow to run Cocoon in a different environment > which provides *some* features of the servlet environment but not all. > The difference might be subtle, but its not the same. Ah, I wasn't getting that subtle. I was simply saying that I can agree with using the servlet API for _all_ environments. The CLI becomes nothing more than a custom servlet container that uses a servlet to generate its pages. In fact, having said that, it becomes yet another tool that is actually independent of Cocoon - it could be used to crawl pages generated by _any_ servlet, not just the Cocoon one. Regards, Upayavira