aboutsummaryrefslogtreecommitdiffstats
path: root/org.eclipse.jgit.test/exttst/org/eclipse/jgit/patch
diff options
context:
space:
mode:
authorChristian Halstrick <christian.halstrick@sap.com>2013-08-04 22:49:47 +0200
committerChristian Halstrick <christian.halstrick@sap.com>2014-02-18 21:04:10 +0100
commit38c4f35d8b911426e007716697b37d746740b788 (patch)
tree8c199a7fc9e2b65135cb388ddec588b212fa79fe /org.eclipse.jgit.test/exttst/org/eclipse/jgit/patch
parentf08fde3eebc2689210292d78db785f6ec52dc8ef (diff)
downloadjgit-38c4f35d8b911426e007716697b37d746740b788.tar.gz
jgit-38c4f35d8b911426e007716697b37d746740b788.zip
Introduce an abstraction for HTTP connections
Previously all HTTP communication was done with the help of java.net.HttpUrlConnection. In order to make JGit usable in environments where the direct usage of such connections is not allowed but where the environment provides other means to get network connections an abstraction for connections is introduced. The idea is that new implementations of this interface will be introduced which will not use java.net.HttpUrlConnection but use e.g. org.apache.client.http.HttpClient to provide network connections. One example: certain cloud infrastructures don't allow that components in the cloud communicate directly with HttpUrlConnection. Instead they provide services where a component can ask for a connection (given a symbolic name for the destination) and where the infrastructure returns a preconfigured org.apache.http.client.HttpClient. In order to allow JGit to be running in such environments we need the abstraction introduced in this commit. Change-Id: I3b06629f90a118bd284e55bb3f6465fe7d10463d Signed-off-by: Christian Halstrick <christian.halstrick@sap.com> Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
Diffstat (limited to 'org.eclipse.jgit.test/exttst/org/eclipse/jgit/patch')
0 files changed, 0 insertions, 0 deletions