CometD is a library collection that allows developers to write web messaging applications: you can send messages from servers to client, from clients to servers, from clients to other clients (via servers), and from server to server (using its clustering
HTTP/2 Push with experimental Servlet API
As promised on my last post on HTTP/2, we have implemented and deployed the HTTP/2 Push functionality on this very website, webtide.com. For the other HTTP/2 implementers out there, if you request “/” on webtide.com, you will get “/wp-includes/js/jquery/jquery.js” pushed.
CometD 3: RPC, PubSub, Peer-to-Peer Web Messaging
A couple of months ago the CometD Project released its third major version, CometD 3.0.0 (announcement). Since then I wanted to write a blog about this major release, but work on HTTP 2 kept me busy. Today CometD 3.0.1 was
HTTP/2 Interoperability and HTTP/2 Push
Following my previous post, several players tried their HTTP/2 implementation of draft 14 (h2-14) against webtide.com. A few issues were found and quickly fixed on our side, and this is very good for interoperability. Having worked many times at implementing
HTTP/2 draft 14 is live !
Greg Wilkins (@gregwilkins) and I (@simonebordet) have been working on implementing HTTP/2 draft 14 (h2-14), which is the draft that will probably undergo the “last call” at the IETF. We will blog very soon with our opinions about HTTP/2 (stay
Jetty 9.1.4 Open Sources FastCGI Proxy
I wrote in the past about the support that was added to Jetty 9.1 to proxy HTTP requests to a FastCGI server. A typical configuration to serve PHP applications such as WordPress or Drupal is to put Apache or Nginx
How to install JIRA 6.1 in Jetty 9.1
Atlassian JIRA is a very good issue tracking system. Many open source projects use it, including our own CometD project and most notably OpenJDK. While Atlassian supports JIRA on Tomcat, JIRA runs in Jetty as well, and can benefit of
WordPress & Jetty: perfect fit
I posted a while back about the capability of Jetty 9.1’s HttpClient to speak HTTP over different transports: by default HTTP, but we also provide a SPDY implementation, where the HTTP requests and responses are carried using the SPDY transport
Speaking at Devoxx 2013
Thomas Becker and I will be speaking at Devoxx, presenting two BOFs: HTTP 2.0/SPDY and Jetty in depth and The Jetty Community BOF. The first is a more technical session devoted to the internals of SPDY and HTTP 2.0, while
Pluggable Transports for Jetty 9.1's HttpClient
In Jetty 9, the HttpClient was completely rewritten, as we posted a while back. In Jetty 9.1, we took one step forward and we made Jetty’s HttpClient polyglot. This means that now applications can use the HTTP API and semantic