Just like GWT generates different JavaScript files for each browser (user agent), gwt-log will cause different JS files for each compile time log level. Combined you will get different JS files for each combination of user agent / compile time log level.
In other words, users running log level WARN or ERROR should not pay the price of any of the logging at lower levels such as debug. Be sure you are checking the size of the JS being sent to the browser, not the total amount of JS being generated. Fred On Tue, Aug 28, 2012 at 4:18 PM, Sri <[email protected]> wrote: > Hello, > Our app is huge and we have recently moved to gwt. We love the gwt-log > features and would in-fact like to have it in even in prod. If any of our > client report problems, our troubleshooting team can ask the user to add > ?log_level=DEBUG (or atleast WARN/ERROR) to url and re-run the scenario... > but the problem we're facing is the size of the JS files that are loaded. > When we tested on chrome, without gwt-log enabled, the size of the JS file > was around 1.6 MB. When compiled with log-level set to DEBUG the size of > the loaded JS was 4 MB. Is there a way to dynamically enable(load) logging. > What is the best way to mitigate this? Thanks in advance. > > -sri > > -- > You received this message because you are subscribed to the Google Groups > "gwt-log" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/gwt-log/-/bjIv4gnBJCkJ. > 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/gwt-log?hl=en. > -- Fred Sauer [email protected] -- You received this message because you are subscribed to the Google Groups "gwt-log" 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/gwt-log?hl=en.
