Mark Thomas (email@example.com) gave an update on the Apache Tomcat roadmap on the first day of the SpringOne Platform conference in Las Vegas this week, in which he brought up the fact that the ongoing delays to Java EE 8, something we've highlighted on InfoQ before, are also causing problems for the Apache Tomcat team.
Java EE 7 introduces a number of new APIs and changes to existing APIs that cater to web developers using HTML5. There are three areas of interest: a new API for working with JSON, a significant update to JSF for working with new attributes, and a new API for working with the WebSocket protocol, one of a variety of technologies that make up HTML5.
VMware's SpringSource team have recently announced plans for Spring 4.0, the next update to the framework, with new features including support for Java SE 8, Groovy 2, parts of Java EE 7, and WebSockets. InfoQ spoke to Spring framework co-founder Juergen Hoeller to find out more about the plans.
Atmosphere 1.0 is a new Java/Scala/Groovy framework that attempts to abstract asynchronous communication between the web browser and the application server. It transparently supports Web Sockets, HTML5 Server Side events and other application server specific solutions when available, with long polling as a fallback.
Lori MacVittie has recently posted an article describing why she believes SPDY will gain much wider acceptance in the Web than WebSockets. For her and several others, the differentiating aspect between these protocols is the way in which they use HTTP and SPDY wins because of this.
Rackspace's Mark Nottingham, discusses the recent HTTPbis Working Group meeting, clarifications to the HTTP/1.1 specification, and the influence of SPDY on the group that have resulted in a change to its charter enabling them to begin considering HTTP/2.0.
As both the WebSocket Protocol and the WebSocket API gain full-fledged support in the Windows 8 Consumer preview, ASP.NET developers can start taking advantage of the bidirectional capabilities by using System.Web.WebSockets library.
Lori Macvittie recently raised concerns about WebSockets vulnerabilities to viruses and malware due to the removal of HTTP headers and MIME types. Given other reported security issues with the protocol and implementations, is it time to step back and consider what a world based on WebSockets should look like?
With WebSockets now a W3C Candidate Recommendation and a new JSR about to start in the JCP, the question arises about how and if WebSockets work with the principles of REST? Do they compliment each other, or will WebSockets, as some people believe, divert attention away from REST and towards a new style of interaction for the Web? There is even the suggestion that WebSockets "breaks the Web".
Last week Microsoft launched HTML5 Labs where they intend to post early prototypes of applications running on unstable web standard specifications for .NET developers. Yet earlier this month, preliminary WebSocket implementations in FireFox 4 and Opera where disabled due to security concerns.