This is the second blog entry on series of blogs about JAX-RS 2.0 Early Draft. Today I'd like to discuss the Generic Interface for building and submitting requests in the Client API. See last week's blog for an introduction to the Client API.
The Early Draft for JAX-RS 2.0 (JSR 339) has been submitted for publication. I plan to use this blog to highlight the features in the new spec, and in this entry I'll start with the most requested feature: the Client API. This API can be broadly divided into 4 areas: the fluent API, the generic interface, configuration and asynchronous support. In this blog entry we'll explore the fluent API.
In my last blog entry, I described VideoSharing which is an application that uses Web sockets to remote UI events and enable participants to control HTML5 video players remotely. Today, I'd like to share with you a similar type of collaboration application, but this time one that uses other HTML5 features: namely, 2D canvases and client SQL databases. The name of this application is...
Some of you may have heard about the recent support for Web Sockets in Grizzly and Glassfish. In this blog, I will show you a simple Web application called <em>VideoSharing</em>. VideoSharing is web application in which you can control and HTML5 video object remotely using Web Sockets and Glassfish. The basic idea is to intercept video events like "play", "pause" and "seeked" and remote them using Web Sockets to control another player. Although there may be some use cases for an app like this (e.g., coaching), the real objective of this exercise is to the low-latency of the Web sockets implementation in Grizzly/Glassfish.