<div dir="ltr">On Fri, Mar 31, 2017 at 11:02 AM, Tristan Tarrant <span dir="ltr"><<a href="mailto:ttarrant@redhat.com" target="_blank">ttarrant@redhat.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You understood incorrectly.<br>
The only change to the Hot Rod clients is that, if they get a 400 error<br>
from a HR PING request, they will initiate an upgrade to Hot Rod and<br>
then proceed with the usual Hot Rod protocol after that.<br>
<br></blockquote><div><br></div><div>Thanks for the clarification. Still, after the HR protocol is negotiated, communication will go<br>through a router, thus adding an extra hop? <br></div><div><br></div><div>Gustavo<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Tristan<br>
<span><br>
On 31/03/2017 11:58, Gustavo Fernandes wrote:<br>
> Hi Sebastian,<br>
><br>
> If I understood it correctly, all the Hot Rod clients will be changed<br>
> from using:<br>
><br>
> - Binary over TCP, circa 40 bytes header, no hops to contact the server,<br>
> no protocol negotiation, no encryption (default)<br>
><br>
> to<br>
><br>
> - HTTP/2 with SSL, protocol upgrade negotiation, and a hop (router) to<br>
> connect to the server.<br>
><br>
><br>
> Any idea of how significant would be this extra overhead introduced?<br>
><br>
><br>
> Thanks,<br>
> Gustavo<br>
><br>
><br>
> On Thu, Mar 30, 2017 at 2:01 PM, Sebastian Laskawiec<br>
</span><div><div class="m_5582656381114831737h5">> <<a href="mailto:slaskawi@redhat.com" target="_blank">slaskawi@redhat.com</a> <mailto:<a href="mailto:slaskawi@redhat.com" target="_blank">slaskawi@redhat.com</a>>> wrote:<br>
><br>
> Hey!<br>
><br>
> My plan is to start working on a Single Point support for Infinispan<br>
> Server very soon and I prepared a design:<br>
> <a href="https://github.com/infinispan/infinispan/pull/5041" rel="noreferrer" target="_blank">https://github.com/<wbr>infinispan/infinispan/pull/<wbr>5041</a><br>
> <<a href="https://github.com/infinispan/infinispan/pull/5041" rel="noreferrer" target="_blank">https://github.com/infinispa<wbr>n/infinispan/pull/5041</a>><br>
><br>
> As you can see I did not use our Wiki (as we used to) because it<br>
> doesn't support inline comments (which is pretty bad in my opinion).<br>
> I would like to propose to keep all the designs along with our<br>
> source code. This approach has been successfully used by the<br>
> Kubernetes [1] folks (although they migrated designs into the new<br>
> Community repository [2] recently). I think it might be a good idea<br>
> to do something similar.<br>
><br>
> Feedback on both items is more than welcome.<br>
><br>
> Thanks,<br>
> Sebastian<br>
><br>
> [1]<br>
> <a href="https://github.com/kubernetes/kubernetes/tree/master/docs/proposals" rel="noreferrer" target="_blank">https://github.com/<wbr>kubernetes/kubernetes/tree/<wbr>master/docs/proposals</a><br>
> <<a href="https://github.com/kubernetes/kubernetes/tree/master/docs/proposals" rel="noreferrer" target="_blank">https://github.com/kubernete<wbr>s/kubernetes/tree/master/docs/<wbr>proposals</a>><br>
> [2]<br>
> <a href="https://github.com/kubernetes/community/tree/master/contributors/design-proposals" rel="noreferrer" target="_blank">https://github.com/<wbr>kubernetes/community/tree/<wbr>master/contributors/design-<wbr>proposals</a><br>
> <<a href="https://github.com/kubernetes/community/tree/master/contributors/design-proposals" rel="noreferrer" target="_blank">https://github.com/kubernete<wbr>s/community/tree/master/<wbr>contributors/design-proposals</a>><br>
><br>
> _____________________________<wbr>__________________<br>
> infinispan-dev mailing list<br>
</div></div>> <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.<wbr>org</a> <mailto:<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.j<wbr>boss.org</a>><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailm<wbr>an/listinfo/infinispan-dev</a><br>
> <<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mail<wbr>man/listinfo/infinispan-dev</a>><br>
<span class="m_5582656381114831737im m_5582656381114831737HOEnZb">><br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">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/mailma<wbr>n/listinfo/infinispan-dev</a><br>
><br>
<br>
</span><span class="m_5582656381114831737HOEnZb"><font color="#888888">--<br>
Tristan Tarrant<br>
Infinispan Lead<br>
JBoss, a division of Red Hat<br>
</font></span><div class="m_5582656381114831737HOEnZb"><div class="m_5582656381114831737h5">______________________________<wbr>_________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">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/mailma<wbr>n/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br></div></div>