Hmm, this is interesting. The size of a frame and its id are at fixed
positions. Bytes 1,2 are length, 3,4 are type and 5,6,7,8 are the id. I'm
just not sure I could get multiple frames received on a single socket to
independently route through different backends, and for response frames to
go
Greetings,
On 7/10/16 6:33 AM, Matt Esch wrote:
> I need to load balance a custom tcp protocol and wonder if HAProxy
> could be configured or extended for my use case.
>
> The protocol is a multiplexed frame-based protocol. An incoming socket
> can send frames in arbitrary order. The first 2
I need to load balance a custom tcp protocol and wonder if HAProxy could be
configured or extended for my use case.
The protocol is a multiplexed frame-based protocol. An incoming socket can
send frames in arbitrary order. The first 2 bytes dictate the frame length
entirely (so max 64k per
3 matches
Mail list logo
