Home

Add a comment

 

Re: Tomcat, WebSockets, HTML5, jWebSockets, JSR-340, JSON and more

@Nelson You're right that Atmosphere doesn't add WebSockets capability to a container/server. But I've to make some things clear so that other readers won't interpret that statement in the wrong way. As its name implies, it's a framework to be used by application developers, not a server implementation. To the application developer, the main thing to be concerned is a usable API to develop AJAX push or WebSockets-style applications, and for that Atmosphere is designed for. At deployment time, if the server AND browser supports WebSockets natively (like GlassFish 3.1, but not limited to), Atmosphere will use it. But if not, the application still continues to work using "degraded" technology (Comet, long-polling, etc.) Win for all parties!!

Re: Tomcat, WebSockets, HTML5, jWebSockets, JSR-340, JSON and more


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).