Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Mime-Version: 1.0 (Apple Message framework v613)
In-Reply-To: <40B62953.9060701@apache.org>
References: <c91jna$ci9$1@sea.gmane.org>
  <646A9588-AEF1-11D8-A676-000A958B684A@outerthought.org>
  <c91n1q$kcv$1@sea.gmane.org>
  <6A6A2D82-AF08-11D8-9FFB-000A958B684A@outerthought.org>
  <40B4BB7A.6040908@apache.org>
  <494EBF82-AF47-11D8-A585-000A958B684A@outerthought.org>
  <40B50E9D.9090901@apache.org>
 <36264.10.0.0.5.1085616298.squirrel@ags01.agsoftware.dnsalias.com>
 <7BA45DC8-AFDA-11D8-8AC9-000A958B684A@outerthought.org>
 <40B62953.9060701@apache.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4A81E888-B02A-11D8-9FF9-000A95C8D3F8@apache.org>
Content-Transfer-Encoding: 7bit
From: Gianugo Rabellino <gianugo@apache.org>
Subject: Re: Stabilizing Javaflow (was Re: Fed up with build discussions:
 proposed deal)
Date: Fri, 28 May 2004 00:07:49 +0200
To: dev@cocoon.apache.org

On May 27, 2004, at 7:45 PM, Sylvain Wallez wrote:
>>
>>> I am podering if is a worth to merge Rhino jar or if is better to 
>>> create
>>> another implementation with Groovy.... or both?:-D
>>
>>
>> For these and other issues, we are unfortunately being forced now to 
>> do our own thing in order to provide our customer with something we 
>> are able to support and defend both technically and legally. I'll 
>> miss the continuations concept though. :-/

I wish this something discussed here in advance since we could have 
maybe found a good way to work together a solution, but I understand 
it's your business. Yet...

> Doesn't the solution reside in javaflow? It does support continuations 
> and has no licence issues. It can even be compatible with JS 
> flowscript by intrumenting Rhino-generated classfiles instead of using 
> the continuations-enabled interpreter.
>
> Sure, it's too late now for your project, but it's IMO a good 
> long-term solution as it provides a single infrastructure to 
> continuation-enable any language compiling to bytecodes: Java, JS, 
> Groovy, Jython, etc.
> So we may decide to concentrate on stabilizing javaflow to finally 
> drop the forked Rhino.
> WDYT?
>

I'd love that. OTOH I recall Cristopher saying something structural 
about the current javaflow not being able to work. Can't find the 
thread ATM, but I sure hope we can circumvent this overcoming. The 
world needs continuations! :-)

Ciao,
-- 
Gianugo Rabellino
Pro-netics s.r.l. -  http://www.pro-netics.com
Orixo, the XML business alliance: http://www.orixo.com