Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Re: [PATCH] tcp: add TCP keepalive tuning options
Date: Fri, 21 Nov 2025 19:05:55 +0100
Message-ID: <aSCqAx-_6RFXR8Wq@phare.normalesup.org> (raw)
In-Reply-To: <20251121174525.3784-1-cordacct2001@gmail.com>

Practice2001 via ffmpeg-devel (HE12025-11-21):
> Addition of tcp_keepalive, tcp_keepidle, tcp_keepintvl, and tcp_keepcnt
> support to the TCP protocol. Exposeing these options to the HTTP protocol
> so they can be used for HTTP(S) connections. Updated documentation.
> Tested with: ./configure && make && make fate

I am rather against this. We already have the option to enable it, which
is necessary.

But tweaking the parameters… Every time I have seen somebody want to do
it, it was for the wrong reasons, to control user-visible timeouts.
These settings are not designed for that and do not offer enough control
to do it accurately.

The fact that the proposal talks of using it in HTTP but not how is not
encouraging.

The fact that it does not work on Windows is also an indication: we
cannot rely on them to implement features.

Let us just close #11671 as wontfix.

Regards,

-- 
  Nicolas George
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-11-21 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 17:45 [FFmpeg-devel] " Practice2001 via ffmpeg-devel
2025-11-21 18:05 ` Nicolas George via ffmpeg-devel [this message]
2025-11-21 18:45   ` [FFmpeg-devel] " Discord Account via ffmpeg-devel
2025-11-24 13:21 ` Nicolas George via ffmpeg-devel
2025-11-24 13:22   ` Nicolas George via ffmpeg-devel
  -- strict thread matches above, loose matches on Subject: below --
2025-11-20 22:25 [FFmpeg-devel] " Practice2001 via ffmpeg-devel
2025-11-24 13:22 ` [FFmpeg-devel] " Nicolas George via ffmpeg-devel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aSCqAx-_6RFXR8Wq@phare.normalesup.org \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=george@nsup.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git