That number (500kb) seems huge for a simple app. Most of our apps in production run around 250kb. One thing you can check is that you aren't using Object or Serializable for RPC arguements or return types (or any type with a large number of subclasses, or loosely-typed collections) -- I'm not even sure that the 1.5 compiler will accept these. There are several warnings about this in the docs..
On Jan 23, 6:47 pm, RamiK <[email protected]> wrote: > Hi, > > I will be developing an enterprise product and am considering GWT and > GXT as the technologies to base my webapp on. I already have an > existing product based on an Applet and\or JSPs and I want to get rid > of them. > > I have already installed and played around with GWT and I have some > concerns regarding the scalability of GWT. > > It seems to me that, at the end of the day, GWT creates 1 large HTML > file (per browser type) that contains all my code in Javascript. That > works great in small scale but already at this stage, when I have > hardly written anything, the html files are 500kb. > > What will happen when I finish developing my product? Will I end up > with a 10Mb HTML file? The load performance will be terrible, not to > mention that there may be some size limitation in the browser for > length of HTML file or ability to handle thousands of lines of > javascript code (??). > > Are my concerns founded? Is the GWT development team planning on > addressing these issues in a future release? > Did anybody already develop a massive GWT application? How large did > the HTML file get? > > Thanks! > R --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
