Author Archives: oleksiyss

Jersey JSP View running on Grizzly server #2: Jersey 2

In the first part it was described how to run JSP on Grizzly and Jersey 1.x. In this blog we will take the same sample and make it work on Jersey 2.x. @Path(“/”) @Produces(MediaType.TEXT_HTML) public class IndexModel { @GET @Path(“index”) … Continue reading

Posted in Uncategorized | Leave a comment

Grizzly 2.3.4: Client-side Connection Pool

New client-side connection pool API has been introduced in Grizzly 2.3.4. This API is completely different from one provided by Grizzly 1.9.x, it has more features and hopefully is nicer and easier to use 🙂 There are 2 main abstractions: … Continue reading

Posted in Uncategorized | Tagged , , , | 2 Comments

Grizzly 2.3.3: Serving Static HTTP Resources from Jar Files

Besides SPDY updates and SPDY server push support, Grizzly 2.3.3 is coming with another interesting feature – possibility to serve static HTTP resources from jar files, or to be more precise serving static HTTP resources using Java ClassLoader. As we … Continue reading

Posted in Uncategorized | Tagged , , | Leave a comment

Grizzly 2.3.3: SPDY Server Push

Starting with 2.3.3, Grizzly offers support for SPDY server push mechanism. Quote: SPDY enables a server to send multiple replies to a client for a single request.  The rationale for this feature is that sometimes a server knows that it … Continue reading

Posted in Uncategorized | Tagged , , | Leave a comment

Jersey JSP View running on Grizzly server

After I read the stackoverflow question on the subj [1], I decided to try it myself, cause theoretically there shouldn’t have been any problem running JSP on Grizzly. And it was actually true, except configuration part: Jasper classloader, JSP API … Continue reading

Posted in Uncategorized | Tagged , , , | 4 Comments

Optimized WebSocket broadcasting with Grizzly 2.3

One of the features introduced in Grizzly 2.3 is Broadcaster API for WebSockets. There are two reasons for that: Broadcasting is widely used with WebSockets (chat-like usecases) and it’s just good idea to have that API generalized. Significant performance optimization … Continue reading

Posted in Uncategorized | Tagged | Leave a comment