diff options
| author | Joel Martin <github@martintribe.org> | 2011-01-23 20:00:08 -0600 |
|---|---|---|
| committer | Joel Martin <github@martintribe.org> | 2011-01-23 20:00:08 -0600 |
| commit | 58995c6f10319ec11f3a810a7bd81b4b9a28925e (patch) | |
| tree | a64c9357239143bb244b872a901fba75081464ec /docs | |
| parent | 49b47baf13a5be19f7da51b5bb263575513440aa (diff) | |
| download | websockify-58995c6f10319ec11f3a810a7bd81b4b9a28925e.tar.gz | |
Typo.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/latency_results.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/latency_results.txt b/docs/latency_results.txt index d42447a..454a590 100644 --- a/docs/latency_results.txt +++ b/docs/latency_results.txt @@ -9,10 +9,10 @@ The latency measure are from the point the packet was sent to when it was received back again in milliseconds. One notable data point missing from this is how long it actually took for the client to send 3000 packets because sending large packets can put load on the browser -and it may be a lot longer than 10ms before the timer to send the next -event fires. So even with low latency numbers, the actual send rate -may be fairly low because sending the WebSockets frames is impacting -the performance of the browser in general. +and it may be a lot longer than 10ms before the timer event to +send the next packet fires. So even with low latency numbers, the +actual send rate may be fairly low because sending the WebSockets +frames is impacting the performance of the browser in general. ------------------------------------------------------------ |