Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
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 10:55:09 +0100 (CET)
Message-ID: <Mutqzr0--3-2@lynne.ee> (raw)
In-Reply-To: <CAPd6JnF+FU-jz7s59w1+KjA=gSUXEhokqXuDjk=LZVVRoeC+pw@mail.gmail.com>

2 Feb 2022, 03:51 by markg85@gmail.com:

> On Wed, Feb 2, 2022 at 3:29 AM Lynne <dev@lynne.ee> wrote:
>
>> 1 Feb 2022, 22:58 by markg85@gmail.com:
>>
>> > This patch adds support for:
>> > - ffplay ipfs://<cid>
>> > - ffplay ipns://<cid>
>> >
>> > IPFS data can be played from so called "ipfs gateways".
>> > A gateway is essentially a webserver that gives access to the
>> > distributed IPFS network.
>> >
>> > This protocol support (ipfs and ipns) therefore translates
>> > ipfs:// and ipns:// to a http:// url. This resulting url is
>> > then handled by the http protocol. It could also be https
>> > depending on the gateway provided.
>> >
>> > To use this protocol, a gateway must be provided.
>> > If you do nothing it will try to find it in your
>> > $HOME/.ipfs/gateway file. The ways to set it manually are:
>> > 1. Define a -gateway <url> to the gateway.
>> > 2. Define $IPFS_GATEWAY with the full http link to the gateway.
>> > 3. Define $IPFS_PATH and point it to the IPFS data path.
>> > 4. Have IPFS running in your local user folder (under $HOME/.ipfs).
>> >
>> > Signed-off-by: Mark Gaiser <markg85@gmail.com>
>> > ---
>> >  configure                 |   2 +
>> >  doc/protocols.texi        |  30 +++++
>> >  libavformat/Makefile      |   2 +
>> >  libavformat/ipfsgateway.c | 267 ++++++++++++++++++++++++++++++++++++++
>> >  libavformat/protocols.c   |   2 +
>> >  5 files changed, 303 insertions(+)
>> >  create mode 100644 libavformat/ipfsgateway.c
>> >
>>
>> Fix all the coding style issues first...
>>
> Any hints on those? As I thought it was matching the other files (looking
> at crypto.c) nicely.
>

https://ffmpeg.org/developer.html#Coding-Rules-1
And we also don't wrap single-line statements in blocks.
_______________________________________________
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".

  reply	other threads:[~2022-02-02  9:55 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
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 [this message]
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=Mutqzr0--3-2@lynne.ee \
    --to=dev@lynne.ee \
    --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