Not Ken Shabby: Imagine here your -exact- reply, except swap 'tomcat' (note: it's not an acronym, you don't need to capitalize it. Jetty isn't either) with 'jetty' and vice versa.
In other words, your argument is only relevant for you. It makes for an excellent reason to switch for those running the end result on jetty. On Nov 26, 3:55 am, Not Ken Shabby <[EMAIL PROTECTED]> wrote: > I will be using TOMCAT as the target server for the foreseeable > future. > > My concern with switching to JETTY within the development environment > is that bugs / issues with the interaction of GWT and TOMCAT may not > be seen / address as quickly as they might otherwise be. > > There may also be some "psychological / political" effect --- "oh, GWT > is something that works with Jetty, it used to work with Tomcat but > they changed it" > > On Oct 20, 10:46 am, 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 Google-Web-Toolkit@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
