<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jun 26, 2016 at 5:11 AM, Max Rydahl Andersen <span dir="ltr"><<a href="mailto:manderse@redhat.com" target="_blank">manderse@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The current release of the openshift-restclient-java, for not so obvious<br>
reasons, depends on no less then 3 libraries to provide the underlying<br>
communication to the cluster server. The following PR<br>
<a href="https://github.com/openshift/openshift-restclient-java/pull/179" rel="noreferrer" target="_blank">https://github.com/openshift/openshift-restclient-java/pull/179</a> unifies<br>
this dependency to a single client which is based on OkHttp. We are<br>
looking to make this change to:<br>
<br>
* Provide a common way to make REST calls<br>
* Simplify the authorization semantics to an openshift cluster<br>
* Simplify the pattern of making REST calls over what is done today<br>
* In future, take advantage of its SPDY support to move away from the oc<br>
binary dependency<br>
* Put us in a better position to move to the Fabric8 client (if that ever<br>
happens)<br>
<br>
Any comments or objects are welcome<br>
</blockquote>
<br></span>
0) "In future" about SPDY - what does that mean ? Can OKhttp already talk with SPDY<br>
on Java 8 without changing the bootclasspath ?<br>
<br></blockquote><div>This client already supports both SPDY and HTTP/2. I plan to do further tests to verify what can be done with the SPDY support but implementing puts us in no worse of a position now IMO. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
1) did you look at the work Stuart Douglas did ? (see mail thread: "ALPN in Java")<br>
Would that be a better option for SPDY ? That would work for Java 8 at least.<br></blockquote><div> </div><div>I think if we EVER anticipate unifying a client with fabric8 our best option is to start with dependency on some of the libraries they use. OkHttp has SPDY support which I believe is just a matter of understanding what we can do with it. At a minimum, this library is significantly easier IMO to use then either jetty, apache client, or the home grown client we were using.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
2) will this integrate with use of proxy settings etc. configured in Eclipse ?<br>
that is what ECF today does for normal http URL connections, if you are using<br>
a separate library my guess is that it is ignoring proxy and other auth setup<br>
done in eclipse, but I could be wrong.<br>
<br></blockquote><div>It has proxy support as well. I will add that to my check list of items to verify. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
/max<br>
<br>
<br>
/max<br>
<a href="http://about.me/maxandersen" rel="noreferrer" target="_blank">http://about.me/maxandersen</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">--<br>Jeff Cantrill<br>Senior Software Engineer, Red Hat Engineering</div><div dir="ltr">OpenShift Integration Services<br>Red Hat, Inc.<br><b>Office</b>: <a href="tel:703-748-4420" value="+17037484420" target="_blank">703-748-4420</a> | <a href="tel:866-546-8970%20ext.%208162420" value="+18665468970" target="_blank">866-546-8970 ext. 8162420</a><br><a href="mailto:jcantril@redhat.com" target="_blank">jcantril@redhat.com</a><br><a href="http://www.redhat.com" target="_blank">http://www.redhat.com</a><br></div></div></div></div>
</div></div>