The Servlet 3.0 specification is doing rounds of the web these days. Although people have loved to use Servlets for various purposes such as implementing business logic in case of small web applications to using it as a controller in MVC architectures, we are yet to see what power will the new specification unleash to the world of web application development.
The JCP has approved JSR 315 (ballot) starting the process that will develop Servlet 3.0. Servlet 3.0 is intended to be part of Java EE 6 together with approved JSRs like JSF 2.1 and JAX-RS 1.0 and several more yet to be launched.
The new specification suggests to bring in the feature of asynchronicity to Servlets. We still can leverage the asynchronous nature in a JEE application with the use of Ajax. Experts think that the Ajax model has a problem in its working which can be seen in this JETTY Continuations theory . Having an inherent quality of server side asynchronous nature means that we wont be having the need of Ajax altogether! Somebody should correct me if I am wrong here.
If we presume that the server which will be based on the new specification, is bound to handle queues for loads of asynchronous requests, then in my opinion it will make the server performance a little slower. I am yet seen an implementation of of asynchronous JAX WS service, so it might be possible that I am bit outdated on that aspect.
But to all my JEE lovers, its a good news that finally we would have something more to cheer about. The good news is that majority of the JCP members have nodded their heads in favor of JSR 315. You can see through their polling results. I think I would need to get my certification for J2EE 1.4 upgraded but I have no complaints. 😀