Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <4231B6BB.70502@apache.org>
Date: Fri, 11 Mar 2005 10:18:19 -0500
From: Stefano Mazzocchi <stefano@apache.org>
Organization: Apache Software Foundation
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Adding cocoon.suicide() to the FOM API.
References: <4231A8CF.6040001@apache.org>
In-Reply-To: <4231A8CF.6040001@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sylvain Wallez wrote:
> Hi all,
> 
> There are some flowscript use cases where we want to stop the current 
> flowscript without creating a continuation, as we don't want to the user 
> to go back to the script.
> 
> An example is a "login" function where the caller function expects this 
> function to exit only if login is successful, but that has to handle 
> e.g. a registration process that includes a "cancel" button.
> 
> This is currently possible using "FOM_Cocoon.suicide()" which is what is 
> used internally by cocoon.sendPageAndWait (see fom_system.js), and I 
> would like to make this more visible by being available as 
> "cocoon.suicide()".
> 
> Any objection?

hmmm, cocoon.suicide() smells of 'shutdown the whole thing' which is 
kind of allarming :-)

I don't mind the functionality being added, but I would like a less 
worrying name for it.

-- 
Stefano.