[
https://issues.apache.org/jira/browse/CALCITE-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated CALCITE-6529:
---------------------------------
Description:
We are re-creating and setting up a SessionContext object for each HTTP call.
We could use a sessionContext object field for the same purpose, or even
better, just set those properties directly on the HttpClient object.
Every member of HttpSession is duplicated in HttpClient, HttpSession is only
used as an override. Since we have a 1:1 relationship between HttpClient and
HttpSession objects, HttpSession is redundant.
was:
We are re-creating and setting up a SessionContext object for each HTTP call.
We could use a sessionContext method for the same purpose, or even better, just
set those properties directly on the HttpClient object.
Every member of HttpSession is duplicated in HttpClient, HttpSession is only
used as an override. Since we have a 1:1 relationship between HttpClient and
HttpSession objects, HttpSession is redundant.
> Use persistent sessionContext in AvaticaCommonsHttpClientImpl
> -------------------------------------------------------------
>
> Key: CALCITE-6529
> URL: https://issues.apache.org/jira/browse/CALCITE-6529
> Project: Calcite
> Issue Type: Improvement
> Reporter: Istvan Toth
> Priority: Minor
> Labels: pull-request-available
>
> We are re-creating and setting up a SessionContext object for each HTTP call.
> We could use a sessionContext object field for the same purpose, or even
> better, just set those properties directly on the HttpClient object.
> Every member of HttpSession is duplicated in HttpClient, HttpSession is only
> used as an override. Since we have a 1:1 relationship between HttpClient and
> HttpSession objects, HttpSession is redundant.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
