[
https://issues.apache.org/jira/browse/HTTPCORE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558763#comment-16558763
]
Oleg Kalnichevski commented on HTTPCORE-544:
--------------------------------------------
{quote}Right, so the question becomes: What is the lifecycle of an
EndpointDetails object?{quote}
{{EndpointDetails}} can stay in the execution context long after the connection
used to execute the message exchange got released back to the pool or even got
closed.
{quote}Can the Socket TO change during the lifetime of an Endpoint detail. This
I do not know. Do you?{quote}
Of course it can and it does.
I do not know what exactly you are trying to accomplish but In my opinion
socket timeout does not belong to {{EndpointDetails}}.
Oleg
> Add org.apache.hc.core5.http.EndpointDetails.getSocketTimeout()
> ---------------------------------------------------------------
>
> Key: HTTPCORE-544
> URL: https://issues.apache.org/jira/browse/HTTPCORE-544
> Project: HttpComponents HttpCore
> Issue Type: New Feature
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Priority: Major
> Fix For: 5.0-beta3
>
>
> Add {{org.apache.hc.core5.http.EndpointDetails.getSocketTimeout()}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
