[
https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369268#comment-15369268
]
ASF GitHub Bot commented on JENA-576:
-------------------------------------
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/151
As I understand it (for what that's worth) `HttpContext` is mostly about
the idea of a "conversation", so if you've got some kind of session going on,
or a series of request-response cycles that compose some kind of larger
stateful activity, `HttpContext` is where you stash that state/context. (E.g. a
cookie store.) So I guess since we want to provide the kinds of facilities
needed for SPARQL protocols, and authN is definitely part of that story, maybe
we would want to provide `HttpContext` as a sidecar param?
> Upgrade Apache HTTP Client to 4.3
> ---------------------------------
>
> Key: JENA-576
> URL: https://issues.apache.org/jira/browse/JENA-576
> Project: Apache Jena
> Issue Type: Dependency upgrade
> Components: ARQ
> Affects Versions: Jena 2.11.0
> Reporter: Rob Vesse
> Assignee: Rob Vesse
> Priority: Minor
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> As of 2.11.0 ARQ centralizes all HTTP operations through HttpOp which relies
> on Apache HTTP Client. Currently we are using 4.2.3 while the latest stable
> release is actually 4.3.1
> Therefore we should look at upgrading our code to use the latest version
> which may entail some refactoring since there appears to have been some
> breaking changes across the minor version bump which users have seen in usage
> - e.g.
> https://github.com/pyvandenbussche/sparqles/issues/9#issuecomment-27220738
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
