https://issues.apache.org/bugzilla/show_bug.cgi?id=51181
--- Comment #3 from Nikolas <nikolasarmstr...@gmail.com> 2011-05-10 19:38:12 UTC --- You also have to consider the fact that a lot of people are starting *new* projects that use websockets and the first thing you do when starting a new project is search for a server that will support it. I think people pass up using tomcat simply because there is no sign of it being implemented here whereas glassfish is a quick and easy alternative. The point is, even if it would be easier to use tomcat as a solution in some cases, its not even worth asking for it when there are viable alternatives. Websockets are new and therefore the projects that use websockets are new. I'd be willing to bet fewer people are going to "port" their application to websockets than those who are going to start a new one that use websockets. If i'm right, Tomcat will be an afterthought until it gets put in (and it would explain the "lack of interest"). If you don't support websockets, tomcat will start losing serious ground. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
