Try downloading an image or file and seeing how long it takes. That could 
give you a rough idea of their total connection speed/latency. Of course 
you'll need to set no-cache headers and the like to prevent the file from 
caching, so your test is good each time. Simply time when you start the 
request and when it finishes and do the math given the request size. Of 
course that still won't be very accurate, but you'll be able to get a 
good/bad judgement.


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/-/8vWzKFWi11EJ.
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.

Reply via email to