Jetty-6 Continuations introduced the concept of asynchronous servlets to provide scalability
and quality of service to web 2.0 applications such as chat,
collaborative editing, price publishing, as well as powering HTTP based
frameworks like cometd, apache camel, openfire XMPP and flex BlazeDS.
With the introduction of similar asynchronous features in Servlet-3.0, some
have suggested that the Continuation API would be deprecated. Instead,
the Continuation API has been updated to provide a simplified portability run asynchronously
on any servlet 3.0 container as well as on Jetty (6,7 & 8).
Continuations will work synchronously (blocking) on any 2.5 servlet
container. Thus programming to the Continuations API allows your
application to achieve asynchronicity today without waiting for the
release of stable 3.0 containers (and needing to upgrade all your
associated infrastructure). wt58jhp2an
[Read More]
Posted at 02:11AM Jul 06, 2009 by gregw in General | Comments[1]
Now that the 2.4 servlet spec is final, I believe the time is right to start considering the end of life for the API. This may sound a little strange coming from somebody on the JSR and who has spent years writing a servlet container, but I think the API has outgrown it's original purpose and no longer is the best API to go forward with.[Read More]
Posted at 09:44AM Dec 18, 2003 by gregw in Servlets | Comments[0]
