Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 55164 invoked from network); 7 Nov 2003 09:55:33 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 7 Nov 2003 09:55:33 -0000 Received: (qmail 36807 invoked by uid 500); 7 Nov 2003 09:54:48 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 36745 invoked by uid 500); 7 Nov 2003 09:54:48 -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 36682 invoked from network); 7 Nov 2003 09:54:47 -0000 Received: from unknown (HELO out2.smtp.messagingengine.com) (66.111.4.26) by daedalus.apache.org with SMTP; 7 Nov 2003 09:54:47 -0000 X-Sasl-enc: 3muNj+TKkoCaZcp32D/GfA 1068198900 Received: from upaya.co.uk (unknown [213.48.13.34]) by www.fastmail.fm (Postfix) with ESMTP id D2F333D3626 for ; Fri, 7 Nov 2003 04:54:59 -0500 (EST) Message-ID: <3FAB6492.1060306@upaya.co.uk> Date: Fri, 07 Nov 2003 09:23:30 +0000 From: Upayavira User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Respecting the CLI 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 X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I often find myself fielding questions on the user list about why the CLI doesn't work. Sometimes this is down to my own stupidity. Other times, however, it is down to people changing things in Cocoon, and assuming that the servlet is the only environment in which Cocoon runs. This isn't the case. The CLI does exist, and I hope there'll be other environments appearing too (e.g. a mailet one for use with Doco). How can we move to a point where changes that are made to Cocoon are done in an environment agnostic way, rather than with an assumption that the servlet is the only user? Thoughts? Regards, Upayavira