On Feb 10, 2009, at 5:51 AM, Rick wrote:
> Pinging google.com [74.125.45.100] with 32 bytes of data: > > Reply from 74.125.45.100: bytes=32 time=370ms TTL=241 > Reply from 74.125.45.100: bytes=32 time=354ms TTL=241 > Reply from 74.125.45.100: bytes=32 time=340ms TTL=241 > Reply from 74.125.45.100: bytes=32 time=370ms TTL=241 > Reply from 74.125.45.100: bytes=32 time=341ms TTL=241 > > Ping statistics for 74.125.45.100: > Packets: Sent = 5, Received = 5, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 340ms, Maximum = 370ms, Average = 355ms > > It is showing 355ms average time but total time elapsed in starting > pinging and pausing for these 5 packets was 5 seconds. Then avg ping > time should be around 1 sec. Now again I got more confused why it is > showing 355ms. Right, Ping sends one ping every second (by default) regardless of the response time. > When I tried to ping my server, it's avg time was 375 ms. Well, that explains at least 1/3 of your time. you need to set up a little test to see how long things are taking on the server. Do successive requests happen any faster? > I also tested by returning a String value but same problem with it > also. Well, now you know it isn't related to longs. -jason --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
