Project

General

Profile

Story #3058

upgrade HTTPComponents from 4.1.3 to 4.2.1

Added by Rob Nahf over 10 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
d1_libclient_java
Target version:
Start date:
2012-07-09
Due date:
2014-12-15
% Done:

100%

Story Points:
Sprint:

Description

The main rationale for the upgrade is the rewritten connection management code. We may wish to experiment with the fluent interface, but that is likely to be more disruptive to existing code, while at the same time constraining us again to one way of managing connections. (It holds a DefaultHttpClient/PoolingClientConnectionManager) instance in a final static property of org.apache.http.client.fluent.Executor class)

The DefaultHttpClient now instantiates a PoolingClientConnectionManager instead of the now deprecated SingleClientConnManager.

from the apache news page:

This is the first stable (GA) release of HttpClient 4.2. The most notable enhancements included in this release are:
* New facade API for HttpClient based on the concept of a fluent interface. The fluent API exposes only the most fundamental functions of HttpClient and is intended for relatively simple use cases that do not require the full flexibility of HttpClient. However, the fluent API almost fully relieves the users from having to deal with connection management and resource deallocation.
* Redesigned and rewritten connection management code.
* Enhanced HTTP authentication API that enables HttpClient to handle more complex authentication scenarios. HttpClient 4.2 is now capable of making use of multiple authentication challenges and retry authentication with a fall-back scheme in case the primary one fails. This can be important for compatibility with Microsoft products that are often configured to use SPNEGO/Kerberos as the preferred authentication scheme.


Related issues

Related to Java Client - Task #4671: suggest updating the following versions: In Progress 2014-03-31
Related to Java Client - Task #3057: retest CLOSE_WAIT issue once the lib client is complete. In Progress 2012-07-09
Related to Infrastructure - Task #6510: libclient_java 1.3.1 Release Closed 2014-10-06

History

#1 Updated by Rob Nahf about 10 years ago

  • Priority changed from Normal to High
  • Status changed from New to In Progress

done in conman branch.
should include in trunk, and d1_common_java

#2 Updated by Rob Nahf over 8 years ago

  • Status changed from In Progress to Testing
  • % Done changed from 0 to 100

moving to v4.3.3, which is the current latest version

#3 Updated by Robert Waltz over 8 years ago

  • Product Version set to 1.4.0
  • Milestone changed from None to CCI-1.4

#4 Updated by Robert Waltz about 8 years ago

  • Target version set to Release Backlog

#5 Updated by Robert Waltz about 8 years ago

  • Product Version changed from 1.4.0 to *

#6 Updated by Rob Nahf about 8 years ago

  • Target version changed from Release Backlog to CCI-2.0.0

#7 Updated by Rob Nahf about 8 years ago

  • Milestone changed from CCI-1.4 to None

#8 Updated by Robert Waltz about 8 years ago

  • Parent task deleted (#2246)

#9 Updated by Robert Waltz about 8 years ago

  • translation missing: en.field_remaining_hours set to 0.0
  • Target version changed from CCI-2.0.0 to CCI-1.4.1
  • Due date set to 2014-10-17
  • Tracker changed from Task to Story

#10 Updated by Rob Nahf about 8 years ago

  • Product Version changed from * to 1.3.1

#11 Updated by Robert Waltz about 8 years ago

  • Due date changed from 2014-10-17 to 2014-10-07
  • Target version changed from CCI-1.4.1 to CCI-1.5.0

#12 Updated by Rob Nahf about 8 years ago

  • Due date changed from 2014-10-07 to 2014-10-20

#13 Updated by Rob Nahf almost 8 years ago

  • Due date changed from 2014-10-20 to 2014-12-15
  • Status changed from Testing to Closed

successfully tested on the CN in sandbox and stage

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)