Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: error (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <41A3939E.6010100@reverycodes.com>
References: <D2AA5324-3CE8-11D9-B496-000393539234@pcextremist.com>
 <41A3939E.6010100@reverycodes.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <58076549-3D8E-11D9-B496-000393539234@pcextremist.com>
Content-Transfer-Encoding: 7bit
From: Miles Elam <miles@pcextremist.com>
Subject: Re: [RT] function sources
Date: Tue, 23 Nov 2004 12:29:15 -0800
To: dev@cocoon.apache.org

On Nov 23, 2004, at 11:46 AM, Vadim Gritsenko wrote:

> Proposed URI syntax:
>
>   script:myMethod(param1, param2, param3)

Yes!  Much clearer, and it fits well with the existing schema.  Still 
has an issue with escaping commas from the parameters if you're passing 
values from the sitemap matcher.  Perhaps that could be seen as a sane 
matcher parameter issue?

I'm still unclear on how to hook into flow from here.  Are the default 
flow objects (cocoon, continuation, etc.) passed on script 
initialization?  I would imagine so since the request and continuation 
values by definition have to be unique for each client request.  So 
where does this variable injection occur?  Behind the scenes in the 
flow interpreter itself or further up the chain closer to the flow 
function caller?

- Miles Elam