From: Mark Gaiser <markg85@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2 1/1] avformat: Add IPFS protocol support. Date: Wed, 2 Feb 2022 01:50:05 +0100 Message-ID: <CAPd6JnGcrht4jR+-hxwohOc63rO7wCfwQhnkKRJiOPthKD-aFQ@mail.gmail.com> (raw) In-Reply-To: <2d44135b-a3f9-711a-ee60-df38d148db92@rothenpieler.org> On Wed, Feb 2, 2022 at 1:49 AM Timo Rothenpieler <timo@rothenpieler.org> wrote: > On 02.02.2022 01:44, Andreas Rheinhardt wrote: > > Timo Rothenpieler: > >> On 02.02.2022 01:33, Mark Gaiser wrote: > >>> On Wed, Feb 2, 2022 at 1:27 AM Timo Rothenpieler < > timo@rothenpieler.org> > >>> wrote: > >>> > >>>> On 01.02.2022 22:58, Mark Gaiser wrote: > >>>>> +static int translate_ipfs_to_http(URLContext *h, const char *uri, > int > >>>> flags, AVDictionary **options) > >>>>> +{ > >>>>> + const char *ipfs_cid; > >>>>> + const char *protocol_path_suffix = "ipfs/"; > >>>>> + char *fulluri; > >>>>> + int ret; > >>>>> + Context *c = h->priv_data; > >>>>> + int is_ipfs = (av_strstart(uri, "ipfs://", &ipfs_cid) || > >>>> av_strstart(uri, "ipfs:", &ipfs_cid)); > >>>>> + int is_ipns = (av_strstart(uri, "ipns://", &ipfs_cid) || > >>>> av_strstart(uri, "ipns:", &ipfs_cid)); > >>>> > >>>> What's the point of this logic? > >>>> The first half of each check seems pointless, since the second half is > >>>> true for everything the first one would cover. > >>>> > >>> > >>> Hi Time, > >>> > >>> The point it to allow > >>> ipfs://<cid> and ipfs:<cid> > >>> > >>> So for that i want to test for all possible true situations (ipfs://, > >>> ipfs:, ipns:// and ipns:). > >> > >> If the url starts with "ipns://", it obviously also starts with "ipns:", > >> so checking for the longer of the two is pointless. > >> Same for "ipfs:". > > > > You forgot that av_strstart() also sets ipfs_cid which is used later; > > the above code exists to strip the leading protocol part away. > > Ah, yeah. That's a very confusing side effect there. > I guess it's fine, but I can't say I like using it like that. > Since there's a large risk someone else might in the future think the > same and break it. > I'm fine changing it to someone that would feel more intuitive. Do you have a suggestion to make it better? > _______________________________________________ > 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". > _______________________________________________ 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:[~2022-02-02 0:51 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-01 21:58 [FFmpeg-devel] [PATCH v2 0/1] " Mark Gaiser 2022-02-01 21:58 ` [FFmpeg-devel] [PATCH v2 1/1] avformat: " Mark Gaiser 2022-02-02 0:26 ` Timo Rothenpieler 2022-02-02 0:33 ` Mark Gaiser 2022-02-02 0:34 ` Mark Gaiser 2022-02-02 0:39 ` Timo Rothenpieler 2022-02-02 0:44 ` Andreas Rheinhardt 2022-02-02 0:49 ` Timo Rothenpieler 2022-02-02 0:50 ` Mark Gaiser [this message] 2022-02-02 0:54 ` Timo Rothenpieler 2022-02-02 1:14 ` Mark Gaiser 2022-02-02 2:29 ` Lynne 2022-02-02 2:51 ` Mark Gaiser 2022-02-02 9:55 ` Lynne 2022-02-02 13:21 ` Tomas Härdin 2022-02-02 13:56 ` Mark Gaiser 2022-02-02 14:24 ` Timo Rothenpieler 2022-02-02 14:39 ` Mark Gaiser 2022-02-04 10:29 ` Tomas Härdin 2022-02-04 14:21 ` Mark Gaiser 2022-02-02 13:29 ` Michael Niedermayer 2022-02-02 14:23 ` Mark Gaiser 2022-02-03 14:54 ` Michael Niedermayer
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=CAPd6JnGcrht4jR+-hxwohOc63rO7wCfwQhnkKRJiOPthKD-aFQ@mail.gmail.com \ --to=markg85@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