fix for connection latency omission fixes #2077

When you say most systems can't start responding before completely
processing the request body, that implies the SUT Is  narrow and does not
include for example the container like netty or spray, web server, os
network software stack.
Sound reasonable?


It would also be useful to refer back to where our expectations of latency
definition come from

Couple of Google results...

http://jmeter.apache.org/usermanual/glossary.html

http://www.pcmag.com/encyclopedia/term/45944/latency

There's some more info in any case.

See the ticket on document measurements. It needs discussing clearly so
let's not rush it.
On 24 Aug 2014 07:36, "Stephane Landelle" <notifications@github.com> wrote:

> In src/sphinx/general/reports.rst:
>
> > @@ -90,7 +90,7 @@ Latency over time
> >      :alt: LatencyOverTime
> >      :scale: 70
> >
> > -The latency is the duration between the end of the request send and the beginning of the response receive.
> > +The latency is the duration between the start of the request send and the beginning of the response receive.
>
> Why did you change this? Latency is firstByteReceived - lastByteSent. Most
> systems can't start responding beforing completely processing the request
> body.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/gatling/gatling/pull/2081/files#r16634569>.
>