From: Mark Gaiser <markg85@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/5] Early version of IPFS protocol support. Date: Mon, 31 Jan 2022 23:04:25 +0100 Message-ID: <CAPd6JnG+sEhJnss9ZgC_FuUZ3YH9FtYAuRLzX1MrhtJv7m-TqQ@mail.gmail.com> (raw) In-Reply-To: <MuloMhH--3-2@lynne.ee> On Mon, Jan 31, 2022 at 9:26 PM Lynne <dev@lynne.ee> wrote: > Jan 31, 2022, 14:51 by markg85@gmail.com: > > > Signed-off-by: Mark Gaiser <markg85@gmail.com> > > --- > > configure | 1 + > > doc/protocols.texi | 30 ++++++ > > libavformat/Makefile | 1 + > > libavformat/ipfs.c | 202 ++++++++++++++++++++++++++++++++++++++++ > > libavformat/protocols.c | 2 + > > 5 files changed, 236 insertions(+) > > create mode 100644 libavformat/ipfs.c > > > > + > > +static int ipfs_open(URLContext *h, const char *uri, int flags, > AVDictionary **options) > > +{ > > + const char *gatewaysuffix; > > + int ret = 0; > > + Context *c = h->priv_data; > > + > > + if (!av_strstart(uri, "ipfs://", &gatewaysuffix) && > > + !av_strstart(uri, "ipfs:", &gatewaysuffix)) { > > + av_log(h, AV_LOG_ERROR, "Unsupported url %s\n", uri); > > + ret = AVERROR(EINVAL); > > + goto err; > > + } > > + > > + char* ipfs_gateway = "https://ipfs.io/ipfs/"; > > > > That's a no from me. I'd rather have native support rather > than depend on some third party service. Users can just convert > the link themselves if they want to. Surely the IPFS project > has libraries one could use instead. > I'm sorry, that part isn't in the final version. I had sent the patches as I made the implementation. This kinda made this part (and a couple others) weird because a later patch gets rid of it. I'll send the v2 revision as a single patch which will give a clear picture of the changes. No fixed url is in it. Just a little oops from a first time contributor :) > _______________________________________________ > 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-01-31 22:05 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-31 13:51 [FFmpeg-devel] [PATCH 0/5] Add IPFS and IPNS " Mark Gaiser 2022-01-31 13:51 ` [FFmpeg-devel] [PATCH 1/5] Early version of IPFS " Mark Gaiser 2022-01-31 15:59 ` Michael Niedermayer 2022-01-31 16:06 ` James Almer 2022-01-31 16:34 ` Mark Gaiser 2022-01-31 20:26 ` Lynne 2022-01-31 22:04 ` Mark Gaiser [this message] 2022-01-31 13:51 ` [FFmpeg-devel] [PATCH 2/5] Fix up IPNS support Mark Gaiser 2022-01-31 16:00 ` Michael Niedermayer 2022-01-31 13:51 ` [FFmpeg-devel] [PATCH 3/5] Merge IPNS and IPFS handling Mark Gaiser 2022-01-31 13:51 ` [FFmpeg-devel] [PATCH 4/5] Implement logic to determine the IPFS gateway Mark Gaiser 2022-01-31 13:51 ` [FFmpeg-devel] [PATCH 5/5] Fix review feedback Mark Gaiser 2022-01-31 15:46 ` Michael Niedermayer 2022-01-31 16:33 ` Mark Gaiser 2022-01-31 15:52 ` [FFmpeg-devel] [PATCH 0/5] Add IPFS and IPNS protocol support Tomas Härdin 2022-01-31 16:31 ` Mark Gaiser 2022-01-31 20:22 ` Tomas Härdin 2022-01-31 22:00 ` Mark Gaiser 2022-02-01 16:39 ` Tomas Härdin 2022-02-01 21:18 ` Mark Gaiser 2022-02-02 12:51 ` Tomas Härdin 2022-02-02 13:32 ` Mark Gaiser 2022-02-01 10:06 ` Michael Niedermayer 2022-02-01 16:43 ` Tomas Härdin 2022-02-02 13:48 ` Michael Niedermayer 2022-02-04 10:28 ` Tomas Härdin
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=CAPd6JnG+sEhJnss9ZgC_FuUZ3YH9FtYAuRLzX1MrhtJv7m-TqQ@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