Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 1/1] avformat: Add IPFS protocol support.
Date: Thu, 3 Feb 2022 15:54:00 +0100
Message-ID: <20220203145400.GQ2829255@pb2> (raw)
In-Reply-To: <CAPd6JnHueE=QdF2o=Jw--YTCpqB-WSnSFtTkCr1fWdBMz1rAkg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2052 bytes --]

On Wed, Feb 02, 2022 at 03:23:34PM +0100, Mark Gaiser wrote:
> On Wed, Feb 2, 2022 at 2:29 PM Michael Niedermayer <michael@niedermayer.cc>
> wrote:
> 
> > On Tue, Feb 01, 2022 at 10:58:30PM +0100, Mark Gaiser wrote:
[...]
> >
> >
> > > +    AVClass *class;
> > > +    URLContext *inner;
> > > +    char *gateway;
> > > +} Context;
> > > +
> > > +// A best-effort way to find the IPFS gateway.
> > > +// Only the most appropiate gateway is set. It's not actually requested
> > (http call) to prevent
> > > +// a potential slowdown in startup. A potential timeout is handled by
> > the HTTP protocol.
> > > +//
> > > +// When done and the return value is 1, a potential IPFS Gateway is set
> > in the gateway
> > > +// variable in the inner URLContext.
> >
> > > +static int ff_populate_ipfs_gateway(URLContext *h)
> >
> > ff_ prefix seems not needed
> >
> 
> Done. Removed the prefix from both functions.
> For the record, I thought it was mandatory to prefix internal functions
> with "ff_"?

only non static ones, these prefixes are to avoid
conflicing with other things in the global namespace


[...]

> 
> 
> >
> >
> > > +    }
> > > +
> >
> > > +    fscanf(gateway_file, "%[^\n]", gateway_file_data);
> >
> > how large is the array ?
> > how large is the data written into the array ?
> > what is the relation between the 2 ?
> >
> 
> Yeah... I'm going to need more information on that one.
> What do you mean?
> Is this wrong?

the array is fixed length, the string written into it is from
some external file IIRC. 
Maybe i missed a check but to me it seemed like the array end can
be overwritten which is bad


thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Awnsering whenever a program halts or runs forever is
On a turing machine, in general impossible (turings halting problem).
On any real computer, always possible as a real computer has a finite number
of states N, and will either halt in less than N cycles or never halt.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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-03 14:54 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
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 [this message]

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=20220203145400.GQ2829255@pb2 \
    --to=michael@niedermayer.cc \
    --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