On Mon, Dec 15, 2008 at 4:09 AM, BobV <b...@google.com> wrote: > I was trying to demonstrate the practical difference that runAsync > would make when compared to a monolithic deployment to someone today, > and there was no simple way to turn off runAsync that wasn't the > -disableAggressiveOptimizations flag. > > This patch adds an undocumented flag -disableRunAsync that just > disables code-splitting when compiling an app.
FWIW, the *implementation* LGTM. The open question is about whether to keep it as a command-line option or go to a module-file solution. Lex --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
