Reply to comment

I finally found some time to write down all the things I'd like to have (or not have anymore) in Cocoon, and Cocoon 3.0 is probably shaping up.

Now should we still call it Cocoon? More than 3 years after Cocoon brought continuations-driven web applications to the world, many people still consider it as a "rendering engine". A different name would allow to clearly show once for all that it is much more than that. Any ideas?