<div dir="ltr">Maybe a polyglot client?</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 27, 2016 at 12:06 PM, Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne@infinispan.org" target="_blank">sanne@infinispan.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Not my area of expertise, so forgive me if I give no technical feedback..<br>
<br>
So, quite off-topic:<br>
please let's not call it "Uber Client". I've tried it, but I'm still<br>
waiting for my car ride to appear :) Is it always this slow?<br>
<div><div class="h5"><br>
On 27 July 2016 at 07:38, Sebastian Laskawiec <<a href="mailto:slaskawi@redhat.com">slaskawi@redhat.com</a>> wrote:<br>
> Hey guys!<br>
><br>
> Recently I've been looking into ALPN support [1] and studying RFC [2] as<br>
> well as JEP [3]. In short, the Application Layer Protocol Negotiation -<br>
> allows the server and the client to agree which protocol shall be used after<br>
> TLS handshake. It will be supported out of the box in JDK9. For JDK8 you<br>
> need a special Jetty Java agent [4].<br>
><br>
> With ALPN we could build an Uber Client, which would be able to support many<br>
> protocols at the same time (REST, HTTP/2, Hot Rod). We should be able to<br>
> select the protocol during client initialization as well as renegotiate<br>
> existing connection. This could be very convenient for situations when<br>
> connecting to multiple Hot Rod servers and some of them are accessible using<br>
> Hot Rod (the same DC or the same Cloud tenant) and some connections need to<br>
> get through a firewall (HTTP/2, REST).<br>
><br>
> Of course implementing this requires major refactoring in the server<br>
> endpoint as well as in the client. Possibly this is something for Infinispan<br>
> 10 :)<br>
><br>
> WDYT?<br>
><br>
> Thanks<br>
> Sebastian<br>
><br>
> [1] <a href="https://issues.jboss.org/browse/ISPN-6899" rel="noreferrer" target="_blank">https://issues.jboss.org/browse/ISPN-6899</a><br>
> [2] <a href="https://tools.ietf.org/html/rfc7301" rel="noreferrer" target="_blank">https://tools.ietf.org/html/rfc7301</a><br>
> [3] <a href="http://openjdk.java.net/jeps/244" rel="noreferrer" target="_blank">http://openjdk.java.net/jeps/244</a><br>
> [4] <a href="https://github.com/jetty-project/jetty-alpn" rel="noreferrer" target="_blank">https://github.com/jetty-project/jetty-alpn</a><br>
><br>
</div></div>> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</blockquote></div><br></div>