Tuesday Jan 13, 2015

Reactive Jersey Client

One of the common problems of synchronous applications is that they are not using resources in an efficient manner. In a synchronous application, it often happens, for example, that threads are blocked waiting for something to happen.  That is clearly not efficient!  On the other hand, asynchronous applications allows to better utilize those threads but this often comes at a price as it is not that easy to write (complex) asynchronous applications.  Writing asynchronous applications involve having to deal with nested callbacks, the famous "callback hell".  And if the level of nested callbacks is too deep, it can also be very tricky to properly handle errors within the application, etc.

Reactive programming is a popular paradigm used to develop more easily asynchronous applications; it is based around data flows and changes propagations.  This Reactive approach also leads to be more maintainable too as the code is easier to write and understand.

Michal Gajdos of the Jersey Team has just written a series of posts introducing the 'Reactive Jersey Client API', a new generic API allowing end users to utilize the popular reactive programming model when using Jersey Client. 

Wednesday Feb 08, 2012

Grizzly now with AHC-powered WebSocket client

With the recent release of Async HTTP Client (AHC) 1.7.0, Ryan has details on how this impacts Grizzly to essentially provide support for WebSocket clients.


Ryan covers the new grizzly-http-client Maven artifact for AHC and introduces UpgradeHandler, WebSocketListener, WebSocket interfaces for WebSocket support with a short but complete working sample.

With this release, Grizzly now provides support for both sides of the WebSocket wire. Both GlassFish 3.1.2 and of course 4.0 will offer support for the final version of server-side WebSocket. if you're eager to use the technology in your application, then you should try out recent builds of 3.1.2 and let us know how things work for you.

Friday Sep 16, 2011

Jersey 1.9.1 & Grizzly Async (HTTP) Client integration

With the release of Jersey 1.9.1, "conference-driven development" (CDD) is not an empty word. In his blog post Martin shares the Jersey-based JavaOne OAuth Hands-on Lab requirements that lead to this release while the full release notes are here.


Meanwhile, Grizzly 2.x is making good progress and the latest trunk includes integration of Jean-François' Async HTTP Client Library (AHC). Ryan, from the Grizzly team, details the status of the ongoing work on his blog, including plans for a Grizzly bundle that includes the HTTP Codec library (grizzly-http), the AHC library and its Grizzly provider. This should all be out in stable form by Grizzly 2.2.