Same way you'd do it in JS; start a timer, request a resource with a callback to stop the timer. Benchmark against various connections and create your heuristics. Set a timeout as well, so if it's really slow, there is no need to wait for it to return. Obviously you'd want to make sure unique names/headers are set to prevent caching of your benchmarking resource. Be careful though, the user could easily switch connections once the app is loaded, so assumptions may change during runtime, which will frustrate your users.
GWT is great for low bandwidth connections given that it can minify the heck out of your application and reduce loading queries to the absolute bare minimum ( 1: load index page, possibly with inlined nocache file and 2: load permutation with as many inlined resources as possible such as css/images). You'd probably be best off just optimizing your app for everyone rather than selectively degrading the UI. - Joe -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
