Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 46567 invoked from network); 6 Jul 2007 07:16:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Jul 2007 07:16:39 -0000 Received: (qmail 37260 invoked by uid 500); 6 Jul 2007 10:12:38 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 37194 invoked by uid 500); 6 Jul 2007 10:12:38 -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 37183 invoked by uid 99); 6 Jul 2007 10:12:37 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jul 2007 03:12:37 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [216.86.168.179] (HELO mxout-04.mxes.net) (216.86.168.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jul 2007 03:12:30 -0700 Received: from [192.168.0.129] (unknown [80.240.191.89]) by smtp.mxes.net (Postfix) with ESMTP id 26981A3209 for ; Fri, 6 Jul 2007 06:12:08 -0400 (EDT) Message-ID: <468E1570.8080904@apache.org> Date: Fri, 06 Jul 2007 12:12:00 +0200 From: Grzegorz Kossakowski User-Agent: Thunderbird 2.0.0.4 (X11/20070604) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: RT: map:call as generic non-redirecting controller code References: <4683DF1E.902@nada.kth.se> <884F6A4A-DA90-40FC-BFD8-351A0306CC45@nukinetics.com> <468B9869.8070206@nada.kth.se> <468BA762.9040405@apache.org> <468D63B9.6060008@nada.kth.se> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Ellis Pritchard pisze: >> Do you mean that you would have flowscripts like: >> >> myFlowAction() { >> var result = calculateSomething(); >> setReturnData(result); >> } >> >> I would much prefer to just use the return value of the flowscript: >> >> myFlowAction() { >> return calculateSomething(); >> } > > Agreed, the former is clumsy, but easier/less disruptive to implement, > the latter is much more natural and what I was originally aiming at. > > Ok, I'll look out for further feedback, but otherwise submit a patch > using the direct return method for people to review. Just to be sure, do you want to implement something like: <- some protocol to obtain the prepared data [...] Such construct introduces new semantics for sitemap because data returned by will be available _outside_ element. Now it is important what is the scope where the data will be visible. Have you thought about it already? -- Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/