On 24 April 2018 at 22:33, Stephan Holljes <klaxa1...@googlemail.com> wrote:
> Hi all, > > I've discussed this on IRC a bit, but I don't want to exclude those > views that are not present there. > > The consensus seems to be that there are more disadvantages in using > the http server of libavformat than there are advantages. > > This arose partly out of the discussion that there is no way to get a > connected peer's address through the public API (as the filedescriptor > is hidden in private structs). > > The alternatives that were discussed were libmicrohttpd or writing the > whole project as an nginx module. > > Both have their share of advantages and disadvantages. While I have > started to read the documentation on both of these, I can't clearly > point out which is the better choice. > > Most people (including my mentor) spoke out in favor of utilizing nginx. > > I don't really mind using lavf, just decide on an API to expose what you need. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
