[ 
https://issues.apache.org/jira/browse/HTTPCORE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleg Kalnichevski updated HTTPCORE-181:
---------------------------------------

    Fix Version/s: 4.1

Lawrence,

I am not sure the connection level is the right place to collect such data. 
Besides, exactly what kind of data HttpConnectionMetrics to record: the elapsed 
time of the LAST request / response pair, average time, the elapsed time of ALL 
request / response pairs? 

Feel free to submit a patch with the changes you would like incorporated into 
the library. However, I tend to think the protocol level (protocol 
interceptors) should be a better place for collecting such data.

Oleg

> Please add recording of time elapsed between http request sent and http 
> response first byte(s) received to HttpConnectionMetrics.
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HTTPCORE-181
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-181
>             Project: HttpComponents HttpCore
>          Issue Type: Wish
>          Components: HttpCore
>    Affects Versions: 4.0-beta3
>         Environment: N/A
>            Reporter: Lawrence M. Bates
>            Priority: Minor
>             Fix For: 4.1
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> We would like to add to the HttpConnectionMetrics classes the recording of 
> the elapsed time between when the http request was sent and when the first 
> byte(s) was/were received.  In other words, we would like to know how long it 
> is taking a business partner of ours to start streaming data back to us after 
> we have sent them an http request for data.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to