Hi Team,
When using OSGI bundles of http client v4.4 and we use
PoolingHttpClientConnectionManager which is internally using SSLContexts
from org.apache.http.ssl package of http core bundle. Though this package
is availabe in export-package of core manifest, it is not imported by
client bundle imp
On Tue, 2015-02-24 at 17:39 +0530, srihari na wrote:
> Hi Team,
>
> When using OSGI bundles of http client v4.4 and we use
> PoolingHttpClientConnectionManager which is internally using SSLContexts
> from org.apache.http.ssl package of http core bundle. Though this package
> is availabe in export-
Hi All,
Is there plans by Apache http components to support http 2.0?
Thanks,-Tony
Please see https://marc.info/?l=httpclient-commons-dev&m=142434644830689&w=2
Gary
On Tue, Feb 24, 2015 at 10:56 AM, Tony Anecito
wrote:
> Hi All,
> Is there plans by Apache http components to support http 2.0?
> Thanks,-Tony
>
--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Per
Thanks Gary looks like discussions are happening but nothing is ever vary fast.
-Tony
On Tuesday, February 24, 2015 12:08 PM, Gary Gregory
wrote:
Please see https://marc.info/?l=httpclient-commons-dev&m=142434644830689&w=2
Gary
On Tue, Feb 24, 2015 at 10:56 AM, Tony Anecito
wrote
My guess is IT and developers will be pushed to quickly use the new standard
and bypass HC to use a simpler solution in the interim.
Regards,-Tony
On Tuesday, February 24, 2015 12:39 PM, Tony Anecito
wrote:
Thanks Gary looks like discussions are happening but nothing is ever vary f
What do you mean by simpler?
Sendt fra min iPhone
> Den 24. feb. 2015 kl. 20.46 skrev Tony Anecito :
>
> My guess is IT and developers will be pushed to quickly use the new standard
> and bypass HC to use a simpler solution in the interim.
> Regards,-Tony
>
>
> On Tuesday, February 24, 20
Good question. Simpler means no frameworks without all the features and focus
on simple url type calls to take advantage of the performance to begin
with.http 2.0 is mostly about performance. The question is what will be
available this month and beginning next month and who will be early
adopte
Tony, HTTP/2 is 1.1 backwards compatible. If the client doesn't understand
HTTP/2 then it will not elect HTTP/2 features.
From my understanding performance gains are only going to be noticed by the new
push mechanism that allows the server serve up parts of the content that the
server thinks th
Actually there are other pluses. For one the number of sockets will go down
dramatically to one since the data is multiplexed over one socket which the app
server people will really want. Also, there is header compression which for
mobile devices is very important since most of thier communicati
The question for this project IMO is how to best implement HTTP/2 if at all
within the bounds of the current code base. This has nothing to do with the
merits of HTTP/2, there is no need to talk about that. It may be that the
changes are so vast that we'd be better off with a new project and code
b
11 matches
Mail list logo