On Wed, Jul 24, 2024 at 03:48:15PM +0200, Christopher Faulet wrote:
> As announced, the SPOE was finally refactored. This new SPOE will be shipped
> with the 3.1-dev4. It is a full rewrite of the engine, based on a dedicated
> SPOP multiplexer. It means a "spop" proxy mode, used for SPOE backends,
ol will be
kept compatible. The purpose here is to rewrite the engine itself. So it is
above all internal to HAProxy. For the 3.0, the warning about the SPOE will be
changed to notify users some configuration changes should be expected in future
versions. Some other small changes should be expect
to rewrite the engine itself. So it is
above all internal to HAProxy. For the 3.0, the warning about the SPOE will be
changed to notify users some configuration changes should be expected in future
versions. Some other small changes should be expected for the 3.0. But the heavy
lifting will be perfor
Hi list,
We have a few usages of SPOE, mainly:
* HTTP traffic mirroring. It's being discussed on GH, more details here:
https://github.com/haproxy/haproxy/issues/2471#issuecomment-2007261494
* authentication (because we used to have 2 auth methods and it helped
developing one backend to handle t
Hi Lokesh,
On Tue, Mar 26, 2024 at 12:10:53AM +, Lokesh Jindal wrote:
> Hey Willy
>
> Resending this email in case you missed the last one. Let me know if you had
> any follow up questions/comments.
> I saw https://github.com/haproxy/haproxy/issues/2502 created by Christopher -
> looking forw
, March 18, 2024 at 4:55 PM
To: Willy Tarreau
Cc: Abhijeet Rastogi , Christopher Faulet
, haproxy@formilux.org , Aleksandar
Lazic
Subject: Re: About the SPOE
Hey Willy
Please see my response inline below.
- Lokesh
From: Willy Tarreau
Date: Monday, March 18, 2024 at 4:08 AM
To: Lokesh Jindal
Cc
Hey Willy
Please see my response inline below.
- Lokesh
From: Willy Tarreau
Date: Monday, March 18, 2024 at 4:08 AM
To: Lokesh Jindal
Cc: Abhijeet Rastogi , Christopher Faulet
, haproxy@formilux.org , Aleksandar
Lazic
Subject: Re: About the SPOE
Hi Lokesh, Abhijeet, Alex,
First, thanks
Hi Lokesh, Abhijeet, Alex,
First, thanks for jumping into this thread, the purpose of the
deprecation is in a big part to try to collect the requirements
of possibly existing users. Mind you that the rare times we hear
about SPOE is only because of problems, so it's difficult to figure
what to kee
Hi.
On 2024-03-15 (Fr.) 15:09, Christopher Faulet wrote:
Hi all,
It was evoked on the ML by Willy and mentioned in few issues on GH. It is now
official. The SPOE was marked as deprecated for the 3.0. It is not a pleasant
announce because it is always an admission of failure to remove a featur
isolation (as much as possible) and observability,
we will be happy to help develop/maintain it.
- Lokesh
From: Abhijeet Rastogi
Date: Friday, March 15, 2024 at 8:23 AM
To: Christopher Faulet
Cc: haproxy@formilux.org
Subject: Re: About the SPOE
Hi Christopher,
Thank you for starting the
Hi Christopher,
Thank you for starting the discussion here.
>Worst, other parts of HAProxy evolved,
especially applets part, making maintenance ever more expensive.
Can we elaborate on what makes maintenance expensive?
>We must be realistic on the subject, there was no real adoption on the SPOE
Hi all,
It was evoked on the ML by Willy and mentioned in few issues on GH. It is now
official. The SPOE was marked as deprecated for the 3.0. It is not a pleasant
announce because it is always an admission of failure to remove a feature.
Sadly, this filter should be refactored to work properl
12 matches
Mail list logo
