Yeah, I read the source code. It's totally different and imho they
are not continuations. I'm planning on writing an article about this
next week. I looked at the code and what Jetty does is simply halting
the execution in a thread and freeing up a request handling thread
for sub-sequent requests. Afterwards, the thread execution is simply
resumed. There's no variable stack or program counter capturing that
is stored, can be eventually serialized, and is resumed independently
from threads. This also doesn't create a continuation call tree where
previous versions can be called in the future to follow different
trails (ie. for back button support).
Continuations is a hot term nowadays and people seem to be eager to
put this label on their no-quite-there-yet features.
On 17-sep-05, at 10:43, Patrick Lightbody wrote:
> Have you seen Jetty 6 continuation support?
>
>
http://www.mortbay.com/MB/log/gregw/>
> It doesn't look exactly the same, and I'll have to see how much I
> can hook in to changing the stack just before the thread starts
> back up (ie: applying new HTTP parameters), but it might be
> promising. Could be the start of something we can get in to a JSR :)
>
> Any thoughts?
>
>
> _______________________________________________
> Rife-devel mailing list
>
Rife-devel@...
>
http://www.uwyn.com/mailman/listinfo/rife-devel>
>
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
