Re: Naming and discoverability of fetches and converters

2020-09-23 Thread Willy Tarreau
On Wed, Sep 23, 2020 at 11:39:57PM +0200, Tim Düsterhus wrote: > Willy, > > Am 23.09.20 um 23:02 schrieb Tim Düsterhus: > > Yes, such a categorized list would certainly solve most of the current > > pain points of the converter documentation. I probably would even leave > > out the purpose column

Re: Naming and discoverability of fetches and converters

2020-09-23 Thread Willy Tarreau
Hi Tim, On Wed, Sep 23, 2020 at 11:02:47PM +0200, Tim Düsterhus wrote: > Willy, > > please excuse my belated reply. First the weekend was there and then > subsequently I forgot about your email. Well, you don't need to apologize :-) I prefer when design discussions take their time than when

Re: Naming and discoverability of fetches and converters

2020-09-23 Thread Tim Düsterhus
Willy, Am 23.09.20 um 23:02 schrieb Tim Düsterhus: > Yes, such a categorized list would certainly solve most of the current > pain points of the converter documentation. I probably would even leave > out the purpose column and instead relying on a descriptive name + the > current long form

Re: Naming and discoverability of fetches and converters

2020-09-23 Thread Tim Düsterhus
Willy, please excuse my belated reply. First the weekend was there and then subsequently I forgot about your email. Unfortunately no one else wanted to add their 2ct so far :-( I believe this is a topic that could benefit from administrator opinions. Am 18.09.20 um 15:26 schrieb Willy Tarreau:

Re: Different behavior of multiple track-sc0 in haproxy 2.2

2020-09-23 Thread Willy Tarreau
Hi Reinhard, On Mon, Sep 21, 2020 at 03:29:17PM +0200, Reinhard Vicinus wrote: > Hi, > > the following haproxy configuration produces different results with > haproxy 2.0.16 (and 1.8.20) vs 2.2.3 running with "haproxy -f > haproxy.conf -d": > > global >   stats  socket /tmp/haproxy.sock mode

unsubscribe

2020-09-23 Thread Tiago Coutinho