Home

Add a comment

 

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

Hi Rolando, First of all, jWebSocket does not implement a standard. So anything I create there my become out of date when JSR-340 is released. Second of all, the configuration of jWebSocket does not run the code which handles web socket requests in a container, meaning that I as a programmer become responsible for things like resources, transactions, security, concurrency, etc. As an example, in an EJB container, I can get my EJB to have access to a secured, transaction safe resource like a database connection, by just adding an annotation to the field which I want the container to inject. And if I move my code to a different server, because say, I want to sell it as a component, then it is really easy for other people to deploy my code, because it uses standards. It is just a deployment problem and no one has to re-write or modify the code.

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).