Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 54094 invoked from network); 6 Jul 2007 06:26:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Jul 2007 06:26:32 -0000 Received: (qmail 15722 invoked by uid 500); 6 Jul 2007 11:37:11 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 15645 invoked by uid 500); 6 Jul 2007 11:37:11 -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 15633 invoked by uid 99); 6 Jul 2007 11:37:11 -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 04:37:11 -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 04:37:04 -0700 Received: from [192.168.0.129] (unknown [80.240.191.89]) by smtp.mxes.net (Postfix) with ESMTP id 9023CA3228 for ; Fri, 6 Jul 2007 07:36:43 -0400 (EDT) Message-ID: <468E2942.3040709@apache.org> Date: Fri, 06 Jul 2007 13:36:34 +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> <468E1570.8080904@apache.org> <468E19AC.3090704@weitling.net> <468E1A5F.4020508@apache.org> <468E1E65.6050608@weitling.net> In-Reply-To: <468E1E65.6050608@weitling.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Dev at weitling pisze: > I'm not against processing data, I want to avoid introducing a new > protocol. I think that we already have such a protocol, are you aware of xmodule:flow-attr combo? > And functions returning values the classical way (return > myBestStuff;) will reduce readability of the pipeline. For few and/or > small values I'd prefer variables, for many and/or big values one should > think about introduce a generator or transformer weaving the data > directly into the pipeline. By variables do you mean something like {someVar} construct in sitemap and someVar can only contain string value? > Giving even void functions a sense: Doing something when a certain point > in a pipeline is reached not directly touching data flowing through the > pipe. That's what I would be against to. Side effects is the last thing we need in pipelines, IMHO. Personally I would like to see possibility to call function only at the *beginning* of the pipeline and *before* data is even processed. Exactly the same way actions are called today. The point about implementing generator is valid only if you want to implement something generic enough to call it component (generators are components). Implementing use-it-once components is anti-pattern, IMHO. > Hope this was not even more obfuscating :-) No, it clears your position a little. :-) -- Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/