From: Camille Oudot <camille+ffmpeg-devel@voila.events>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/rtpproto: add support for RTP/UDP socket reuse
Date: Wed, 04 Jan 2023 12:24:05 +0100
Message-ID: <7f17349fa6a3ff1564e4211fcbe4aa72fa1b7b6d.camel@voila.events> (raw)
In-Reply-To: <Y7SFR++MwbbCjvGo@phare.normalesup.org>
> Because it is an useful option. Only not for this use case.
> Because nobody noticed it was badly named when it was applied.
>
> > Why would it not apply to "rtp" also?
>
> Because nobody made the UDP socket context a child object of the RTP
> context.
So does it still makes sense to have a patch to pass through a RTP
"reuseaddr" option to the underlying UDP URL "reuse" option?
Documenting the good use cases of course (although I'd start using it
for the wrong use case ;-)). If yes I'll resubmit the patch.
I'm still planning to have a look on a proper (e.g using only one
shared socket) implementation of rtcp-mux (easy one, I already have a
PoC working) and RTP Bundle (tougher one).
Regards
--
Camille
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-01-04 11:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 15:28 Camille Oudot
2022-12-22 15:42 ` Camille Oudot
2022-12-22 19:32 ` Nicolas George
2022-12-24 11:36 ` Rémi Denis-Courmont
2022-12-24 13:07 ` Camille Oudot
2022-12-25 10:00 ` Rémi Denis-Courmont
2022-12-25 23:52 ` Camille Oudot
2022-12-26 3:20 ` "zhilizhao(赵志立)"
2022-12-26 21:47 ` Nicolas George
2022-12-27 0:46 ` "zhilizhao(赵志立)"
2022-12-31 19:34 ` Rémi Denis-Courmont
2023-01-03 9:03 ` Camille Oudot
2023-01-03 16:03 ` Rémi Denis-Courmont
2023-01-03 19:13 ` Camille Oudot
2023-01-03 19:43 ` Nicolas George
2023-01-04 11:24 ` Camille Oudot [this message]
2023-01-05 12:16 ` Nicolas George
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=7f17349fa6a3ff1564e4211fcbe4aa72fa1b7b6d.camel@voila.events \
--to=camille+ffmpeg-devel@voila.events \
--cc=ffmpeg-devel@ffmpeg.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