Re: [infinispan-dev] Single Endpoint design

2017-04-06 Thread Sebastian Laskawiec
The design has been moved here: https://github.com/infinispan/infinispan-designs/pull/2 Are there any last comments? I plan to start working on that shortly. Thanks, Sebastian On Fri, Mar 31, 2017 at 4:20 PM Sebastian Laskawiec wrote: > With TLS+ALPN the use case is very simple. The protocol i

Re: [infinispan-dev] Single Endpoint design

2017-03-31 Thread Sebastian Laskawiec
With TLS+ALPN the use case is very simple. The protocol is negotiated during the handshake. Then the existing TCP connection is reused and the client starts to send Hot Rod binary bits through the wire. Sadly, TLS adds some significant overhead to the transmission. With HTTP/1.1 Upgrade it's a bit

Re: [infinispan-dev] Single Endpoint design

2017-03-31 Thread Tristan Tarrant
No, once the connection is established, I believe the netty pipeline can be trimmed to the necessary elements. Tristan On 31/03/2017 13:57, Gustavo Fernandes wrote: > On Fri, Mar 31, 2017 at 11:02 AM, Tristan Tarrant > wrote: > > You understood incorrectly. >

Re: [infinispan-dev] Single Endpoint design

2017-03-31 Thread Gustavo Fernandes
On Fri, Mar 31, 2017 at 11:02 AM, Tristan Tarrant wrote: > You understood incorrectly. > The only change to the Hot Rod clients is that, if they get a 400 error > from a HR PING request, they will initiate an upgrade to Hot Rod and > then proceed with the usual Hot Rod protocol after that. > > Th

Re: [infinispan-dev] Single Endpoint design

2017-03-31 Thread Tristan Tarrant
You understood incorrectly. The only change to the Hot Rod clients is that, if they get a 400 error from a HR PING request, they will initiate an upgrade to Hot Rod and then proceed with the usual Hot Rod protocol after that. Tristan On 31/03/2017 11:58, Gustavo Fernandes wrote: > Hi Sebastian,

Re: [infinispan-dev] Single Endpoint design

2017-03-31 Thread Gustavo Fernandes
Hi Sebastian, If I understood it correctly, all the Hot Rod clients will be changed from using: - Binary over TCP, circa 40 bytes header, no hops to contact the server, no protocol negotiation, no encryption (default) to - HTTP/2 with SSL, protocol upgrade negotiation, and a hop (router) to con

[infinispan-dev] Single Endpoint design

2017-03-30 Thread Sebastian Laskawiec
Hey! My plan is to start working on a Single Point support for Infinispan Server very soon and I prepared a design: https://github.com/infinispan/infinispan/pull/5041 As you can see I did not use our Wiki (as we used to) because it doesn't support inline comments (which is pretty bad in my opinio