Cometd 2.1 now supports annotations to define cometd services and clients. Annotations greatly reduces the boiler plate code required to write a cometd service and also links well with new cometd 2.x features such as channel initializers and Authorizers, so
The webtide blogs are moving to http://webtide.intalio.com. All new postings from the jetty & cometd team will be made here and over time we will move the content from the old site as well.
Cometd 2.1 now supports annotations to define cometd services and clients. Annotations greatly reduces the boiler plate code required to write a cometd service and also links well with new cometd 2.x features such as channel initializers and Authorizers,
Not too long ago we had a contribution from Angelo Zerr that gave jetty a native WTP adaptor. We are happy to announce its availability now! Shockingly, there is some documentation for this plugin, based on the original documentation provided
I have presented the advanced features of Jetty at the Eclipse Summit Europe 2010. Highlights of the features that I presented are: Jetty & OSGi, showing the full integration of Jetty with the OSGi world Jetty’s asynchronous HTTP client Jetty’s
In July I participated in London to the Comet Panel, organized by the London Ajax User Group. Me and a bunch of other Comet experts talked about our own Comet projects, and I talked about CometD. Here you can watch
A new feature that has been recently added to the upcoming CometD 2.1.0 release is the support for annotated services, both on server side and on client side. Services are the heart of a CometD application, because allow to write
Phil Windley of Tecnometria has recorded an interview with me on Cometd and Push Technology. The podcast is available from ITConversations and provides an introduction to comet and cometd.
With the imminent release of cometd-2.0.0, it’s time to publish some of our own lies, damned lies and benchmarks. It has be over 2 years since we published the 20,000 reasons that cometd scales and in that time we have
Benchmarks like statistics can be incredibly misleading in ways that are only obvious with detailed analysis. Recently the apache HTTPCore project released some benchmark results whose headline results read as: Jetty HttpCore Linux BIO 35,342 56,185 Linux NIO 1,873 25,970