yeah, code spliting is probably the solution... I was hopping a way to apply clipping information on any image. Probably a bad idea ;)
Le jeudi 5 juillet 2012 19:42:45 UTC+2, Joseph Lust a écrit : > > Kroc, > > This is how ClientBundle is intended to work. I bet that loading 300KB is > faster than loading 2000 separate images (~200 packets vs ~4000, assuming > 1514B MTU). > > Consider using code splitting to break out your image resources into > separate bundles so that they are loaded as needed by different modules. > That way you won't need that 300KB download up front. > > See this recent > post<https://groups.google.com/forum/?fromgroups#!searchin/google-web-toolkit/speed/google-web-toolkit/CVvq7tfZUpQ/QbexjSr_APQJ>about > how to cut down on initial download side. > > > > Sincerely, > Joseph > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/sa17pMDCM0MJ. 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.
