They are both very capable servlet containers, used by many. If you really need or want Jetty's WebSockets then it is the deal breaker that selects Jetty.
On Sep 27, 5:32 pm, Markus Unger <markus.unger1...@googlemail.com> wrote: > Hello! > > Currently I use the Tomcat as Servlet Container, but I need to use > WebSockets. So I find the Jetty WebContainer with integrated WebSocket > support. > > I search for some tutorials and looked for some books for jetty as > webserver. But the results are low... > > Is there a good reason why I should not use Jetty instead of Tomcat? > > Thanks for help -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
