If Jetty could get more configurable ( add jar files; bbdd connections, etc.. ) would be a great improvment. Simply using less memory and resources is a step ahead; +1 jetty
For Gregor: both Tomcat and Jetty comply the Java servlet spec, so there are no expected problems on code if GWT swich from one to another. Oskar On 20 oct, 17:46, John <[EMAIL PROTECTED]> wrote: > Manuel Carrasco wrote:The most annoying issue with GWT is performance in > development mode. I mean, compiling, startng hosted mode and running GWT Unit > tests. So any action that improves these is welcome. > So my vote if for jetty > +1 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
