[FFmpeg-devel] [PATCH] IPv6 support v.2

Ronald S. Bultje rsbultje
Thu Nov 8 00:16:17 CET 2007


Hi,

On Nov 7, 2007 10:35 AM, Nicolas George <nicolas.george at normalesup.org>
wrote:

> - Implement a version of getaddrinfo and getnameinfo suitable for
> ffmppeg's
>  needs.
>
> - Drop the IPv4-only code.

[..]

> I just looked at Ronald's code, and I am wondering about his
> inetaddr_resolve function: as far as I can see, it does exactly the same
> as
> getaddrinfo, only with a different API. Is it so?


In part (largely), yes. However, once in, I plan to extend it with good
error handling (see my antique errno patches if you want to know how I got
at this point).

As for making a getaddrinfo() for systems that do have it, I guess that's
another way, but then I wouldn't be able to generalize error handling into
the wrapper, plus that I would risk (and be asking for) symbol clashes,
which is especially bad since I want to export this stuff and have ffserver
use the exported symbols (see other antique patches) rather than the current
hacks. I originally just changed resolve_host() to be ipv6-compatible (and
before that, to have error handling). Only later did I rename it to
inetaddr_*() as the API changed too much.

Anyway, there's multiple ways to get there, I'd prefer this, but it'd be
nice to have a fixed path to take rather than the turns I continuously have
to take now (I hope you can see how it is a tad depressing to not make any
progress on this front for over a year now). If there's no strong
objections, I'd honestly prefer getting this in and continuing from here,
the patches are not so bad imo. We waste too much time on this simple stuff,
I have lots of stuff I would be doing after this (e.g. errno patch
re-visiting, and actually continue my work on userspace applications that
make this stuff available to the average new Linux user that barely knows
what avi is, how to compile ffmpeg or what the verb to compile actually
signifies), but all this gets pushed back more and more as we re-go over old
issues that are not so interesting anymore.

Ronald




More information about the ffmpeg-devel mailing list