[GitHub] [jena] afs commented on issue #1384: Regression: Http connect timeout no longer wired up

[GitBox <gi...@apache.org>]

afs commented on issue #1384:
URL: https://github.com/apache/jena/issues/1384#issuecomment-1155503951

   `HttpConnectionParams` is `org.apache.http.params.HttpConnectionParams`.
   
   Jena now uses `java.net.http.HttpClient`, not Apache HttpClient.
   
   Apache HttpClient is only in the dependencies because jsonld-java uses it. If Titanium becomes the only JSON-LD provider, then it won't be needed. We can probably drop the explicit mention now. jena used to need to control the version.
   
   In `java.net.http`, connection timeout is "TCP connection setup" timeout. See `java.net.http.HttpClient.Builder.connectTimeout` 
   
   > In the case where a new connection needs to be established, ...
   > If a new connection does not need to be established, for example if a connection can be reused
   > from a previous request, then this timeout duration has no effect.
   
   In the case of `RDFConnection`it does reuse the `java.net.http.HttpClient` and hence connections.
   Unless provided, there is only one `HttpClient` 
   
   HTTP/2 : there is no TCP connection setup other that the one shared host-host connection.
   
   HTTP/3 : different again.
   
   QueryExecution.setTimeout is deprecated. There is some compatibility code (hidden delayed building) because there is a "build-use" pattern nowadays -- `QueryExec` does not allow changes of setup after building.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org
For additional commands, e-mail: issues-help@jena.apache.org