From: Basel Sayeh <basel.sayeh@hotmail.com>
To: Steven Liu <lingjiujianke@gmail.com>
Cc: "kjeyapal@akamai.com" <kjeyapal@akamai.com>,
"ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Update for my hls and dash patches?
Date: Thu, 5 Jan 2023 01:19:33 +0000
Message-ID: <DB9P191MB14826B61DB0965FE41E71C81FEFA9@DB9P191MB1482.EURP191.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CADxeRwnQikC39xtg2hDZfJAN2f21oNTDnicF+ZWsv+7D3wu_Ow@mail.gmail.com>
> >
> > Hello,
> >
> >
> > Any update or comment on these patch sets?
> >
> >
> > Enable HTTP persistent connections for hls_delete_file &
> > dashenc_delete_file:
> > https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=8033
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/DB9P191MB14827461396938910246ACE9FE1B9@DB9P191MB1482.EURP191.PROD.OUTLOOK.COM/
>
> You should check the first patch of this series.
Do you mean i should take a look at the warnings?
> >
> >
> > Use http_read_header in http_shutdown to react to response errors:
> > https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=8058
> Is it will use block mode of socket?
Yes, it will wait for a server reply (if not sent), and react to some http errors, like 404
I am aware that it may slow the encoding/sending down, but is there any better way that it can be done?
_______________________________________________
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-05 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 17:12 Basel Sayeh
2023-01-04 2:37 ` Steven Liu
2023-01-05 1:19 ` Basel Sayeh [this message]
2023-01-05 6:26 ` Steven Liu
2023-01-07 0:31 ` Basel Sayeh
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=DB9P191MB14826B61DB0965FE41E71C81FEFA9@DB9P191MB1482.EURP191.PROD.OUTLOOK.COM \
--to=basel.sayeh@hotmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=kjeyapal@akamai.com \
--cc=lingjiujianke@gmail.com \
/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