Hi Willy.
Am 12.11.2018 um 21:01 schrieb Willy Tarreau:
> On Mon, Nov 12, 2018 at 07:42:21PM +0100, Aleksandar Lazic wrote:
>> Even I agree with you to the point that HAProxy should be able to handle this
>> next upcomming/available technology, I'm not sure if it's really a benefit
>> for us, the enduser.
>
> Hey, why do you guys imagine we're suffering that much redesigning all the
> connection management in 1.9 and making HTTP processing version-agnostic ?
> :-)
Well because you love to challenge your self, I'm just kidding ;-)
Oh wow this is really a good time to get the hands dirty as QUIC is a major
design change in HTTP, IMHO.
To adopt the matrix from one of the last message, haproxy will be able to do the
conversion in almost every direction?
HTTP/1.x <> HTTP/2
HTTP/2 <> HTTP/3
HTTP/1.x <> HTTP/3
HTTP/3 <> HTTP/3
Is this technically possible as the UDP/QUIC may have not some information that
the TCP/HTTP need?
As I try to imagine the new design in HAProxy will it look like this?
TCP (TCP|UDP) HTTP/1.x,HTTP/2,HTTP/3
\ /
HTTP/TCP/UDP Engine - (TCP|UDP) HTTP/1.x,HTTP/2,HTTP/3
(Here happen some magic)
/ \
UDP (TCP|UDP) HTTP/1.x,HTTP/2,HTTP/3
Really 8-O ?
What happens with other protocols like plain TCP/UDP or grpc and so on?
Sorry a lot of questions, but you know I'm curious and try to understand some
parts of the future ;-).
> We still have a lot of work to be done before supporting QUIC but we've
> started to have a clear idea how that will fit. The only thing is that
> experience taught us the the devil is in the details, and haproxy has
> accumulated a lot of details over the years.
Oh yes as always, this devil lay there for years and suddenly he jumps out and
say "nana I'm here" 8-O.
> Willy
Cheers
Aleks
