From: Derek Buitenhuis <derek.buitenhuis@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 8/6] doc/protocols: Fill in missing HTTP options Date: Mon, 22 Apr 2024 15:26:24 +0100 Message-ID: <0310c620-2450-4497-b584-09203a5085e6@gmail.com> (raw) In-Reply-To: <Zh6xtN3MP3EY8E2H@mariano> On 4/16/2024 6:13 PM, Stefano Sabatini wrote: >> +@item metadata >> +An exported dictionary containing Icecast metadata from the bitstream, if present. >> +Only useful with the C API. > > Probably best to use impersonal verbal mode: > Set an exported ... This is not quite right. This is not a user-settable option, but exported data from http.c to be read by the user. >> +@item location >> +An exported dictionary containing the content location. Only useful with the C >> +API. > > Ditto Same comment as above. >> +@item reconnect_max_retries >> +Sets the maximum number of times to retry a connection. Default unset. > > Set the ... Done. >> +@item resource >> +The resource requested by a client, when the experimental HTTP server is in use. > > Set the ... It is an export, as noted in a few of the above options, and not user-settable. > also this might be more explicit (what is a resource in this context?) Resource is a standard HTTP term: https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web >> +@item short_seek_size >> +The threshold, in bytes, for when a readahead should be prefered over a seek and >> +new HTTP request. This is useful, for example, to make sure the same connection >> +is used for reading large video packets with small audio packets in between. > > Set the ... > for consistency reasons Done. v2 patch set sent: https://ffmpeg.org//pipermail/ffmpeg-devel/2024-April/326065.html - Derek _______________________________________________ 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:[~2024-04-22 14:27 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-15 16:27 [FFmpeg-devel] [PATCH 0/6] HTTP rate limiting and retry improvements Derek Buitenhuis 2024-04-15 16:27 ` [FFmpeg-devel] [PATCH 1/6] avutil/error: Add HTTP 429 Too Many Requests AVERROR code Derek Buitenhuis 2024-04-15 16:31 ` Andreas Rheinhardt 2024-04-15 16:43 ` Derek Buitenhuis 2024-04-15 16:27 ` [FFmpeg-devel] [PATCH 2/6] avformat/http: Use AVERROR_HTTP_TOO_MANY_REQUESTS Derek Buitenhuis 2024-04-15 16:27 ` [FFmpeg-devel] [PATCH 3/6] avformat/http: Don't bail on parsing headers on "bad" HTTP codes Derek Buitenhuis 2024-04-15 16:27 ` [FFmpeg-devel] [PATCH 4/6] avformat/http: Add support for Retry-After header Derek Buitenhuis 2024-04-15 16:35 ` James Almer 2024-04-15 16:49 ` Derek Buitenhuis 2024-04-15 16:27 ` [FFmpeg-devel] [PATCH 5/6] avformat/http: Rename attempts to auth_attempts Derek Buitenhuis 2024-04-15 16:27 ` [FFmpeg-devel] [PATCH 6/6] avformat/http: Add options to set the max number of connection retries Derek Buitenhuis 2024-04-15 16:43 ` [FFmpeg-devel] [PATCH 1/6] avutil/error: Add HTTP 429 Too Many Requests AVERROR code Derek Buitenhuis 2024-04-15 16:44 ` Derek Buitenhuis 2024-04-15 16:49 ` [FFmpeg-devel] [PATCH 4/6 v2] avformat/http: Add support for Retry-After header Derek Buitenhuis 2024-04-15 17:33 ` Stefano Sabatini 2024-04-16 13:59 ` Derek Buitenhuis 2024-04-16 13:55 ` [FFmpeg-devel] [PATCH 7/6] doc/protocols: Re-order HTTP options to match http.c order Derek Buitenhuis 2024-04-16 13:55 ` [FFmpeg-devel] [PATCH 8/6] doc/protocols: Fill in missing HTTP options Derek Buitenhuis 2024-04-16 17:13 ` Stefano Sabatini 2024-04-22 14:26 ` Derek Buitenhuis [this message] 2024-04-22 14:58 ` Stefano Sabatini 2024-04-16 17:08 ` [FFmpeg-devel] [PATCH 7/6] doc/protocols: Re-order HTTP options to match http.c order Stefano Sabatini
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=0310c620-2450-4497-b584-09203a5085e6@gmail.com \ --to=derek.buitenhuis@gmail.com \ --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