Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: domain of eric.gulatee@gmail.com
 designates 64.233.184.207 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=fnA44UlwUpgPMKkQRafZ+67REB6bUYnZnO22bekohdEdAAQtCKXiFT5yz6PcBKfaKTJQjBsAlxpzY1o0X2aL6GJBuUKZMjRQJLJoQWUL35g0ju7GuoCcHMZXLdqaZGuzQUE1hqG008CwHNr+z7TEnU2qTLCMx+4lFFDBkNxdCuk=
Message-ID: <28dea75b05051510533827320c@mail.gmail.com>
Date: Sun, 15 May 2005 13:53:53 -0400
From: Eric Gulatee <eric.gulatee@gmail.com>
Reply-To: Eric Gulatee <eric.gulatee@gmail.com>
To: dev@cocoon.apache.org
Subject: Re: JavaFlow
Cc: Torsten Curdt <tcurdt@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

> > I've noticed a few items with javaflow from svn under jakarta, when
> > you suspend the continuation, the thread continues executing.  I
> > believe the old javaflow blocked the thread.  With the new javaflow
> > how can you then resume where you "suspended"?

> This is most likely because you are going the "2.1 way"
> of using javaflow.
>
>Javaflow can now be used in two different ways - well
> to be exact three different ways.
>
> The old synchronous way where the rewriting is done inside
> the classloader. And now there is the asynchronous one where
> you point your javaflow to monitor your classes or your sources
> directory. I am not yet sure which way we should settle on.
> This depends a bit on the development vs deployment factor.

I've been going thru commons-javaflow pretty impressive.  :)  I think
I have a deeper understanding what's going on.

I'll stick with the Asynchronous class loader, I will try to make some
changes to it, so it uses ASM instead of BCEL since the use of
Annotations would simplify my dev.  If I ever get to that point, I'll
ask how to submit a patch.

Now digging into Continuations, I'm still perplexed, once you call
suspend(), aside from capturing the stack, nothing happens, the thread
continues execution.
Shouldn't forminstance/abstractcontinuable be stopping the current thread?

Otherwise this means that loops & business logic will get invoked.=20
And It's a rather large pain to detect if the continuation is
suspended in the javaflow code and not execute logic.

Cheers,
Eric.