– by standardising communications between HTML5 clients and Java server side (listed technologies – Websockets, etc. – are however still in use, and Oracle didn’t provide hints about a common JSON description format for describing action messages).
You can make an HTML5 client work with a Java back-end today, but it’s not that fun, it’s not that easy to use, and it’s not that easy for HTML folks to collaborate with Java folks.
HTML5 brings new standard for new and/or existing features (Canvas) provided by browsers, and mainly derived from WebKit advances. However Avatar does not provide abstraction/media layer to these various APIs (Canvas, WebGL, CSS3) that allow to display a modern user interface (in such a way as Cappuccino’s DocumentBridge and implementation of Quartz/Core Animation), nor an applicative framework (such as Cappuccino’s implementation of AppKit).
Finally there is no information about client/server bridge solution (messages serializing, session and profiles management, authentication, access to remote data through cursor, sorting) like CP2JavaWS.