Is there other options to help evaluate during runtime the difference
between server time, client rendering time, and network transport time
outside of using chrome/speedtracer? Something that would help where
users could get feedback and provide information that could be logged
regardless of browser used to show when there are server issues, gwt
issues, or network issues with regards to timeliness?
tia,
-D
On Sep 9, 11:42 am, dhartford binarymon...@gmail.com wrote:
Hey all,
I'm looking at what the LightweightMetrics can supply (opposed to hand-
rolling your own), but it is not clear to me if it handles metrics on
both the client and the server side to capture network latency issues
(or, to be more general, network transport time) inbetween the client
and the server.
client request sent: 1234567890
--network latency:200ms
server receive request: 1234568090 (+/- client/server time offsets)
server sending response: 1234568140 (+/- client/server time offsets)
--network latency:200ms
client receive response: 1234568340
Is this something that I (more than likely) just do not understand
about the current LightweightMetrics, or is this out of scope or
something someone else may have solved with a different approach/
library?
usecase: if you have optimized server and client code as much as
possible, but someone is using dial-up or mobile network connection,
want to be able to identify and record when that occurs.
thanks!
-D
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
