Cometd Features and Extensions
The cometd project is nearing a 1.0 release and thus we are make a bit of a push to improve the project documentation. As part of this effort, we have realized that there are many cool features and extensions to cometd that have been under-publicized. So this blog is an attempt to give a whirlwind tour of cometd features and extensions.[Read More]
Posted at 04:16PM Jul 08, 2009 by gregw in General | Comments[2]
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]
Roadmap for Jetty-6, Jetty-7 and Jetty-8
This blog updates the roadmap for jetty-6, jetty-7 and jetty-8 with the latest plans resulting from the move to the Eclipse Foundation and the delay in the servlet-3.0 specification.[Read More]
Posted at 07:47PM Jul 02, 2009 by gregw in General | Comments[8]
Bidirectional Web Transfer Protocol - BWTP
I really like the idea behind the HTML5 Websocket API - namely that a datagram model should be used for web application communication rather than a request/response paradigm (this is also the idea behind cometd). But unfortunately, the proposed protocol to carry websocket traffic is neither a good protocol nor is it well specified.[Read More]
Posted at 08:38PM Jul 01, 2009 by gregw in General | Comments[1]
The announcement of Google Wave is a bold declaration of where google sees the future of the web. Google, unsurprisingly enough, sees the future of the web as a server side paradigm, with dynamic updates being used to drive the thin client model to capture even more of tasks that where once done client side. Google are extending the server side model of webmail to apply to applications that have been fundamentally client side, such as document authoring, IM and chat.[Read More]
Posted at 05:32PM Jul 01, 2009 by gregw in General | Comments[0]
