Aman Gupta (2017-12-29): > It also makes it easier in the future to add http keepalive support to > other consumers like the dash demuxer and the crypto protocol.
For that, the API does not need to be public, it just need to be clean. I thought you were referring to using the hls demuxer with other protocols that may allow connection reuse. That could justify a public API. But we do not know what kind of parameters these other protocols may need; maybe some of them will require flags to select parallel / sequential requests; maybe one of them will need to return some kind of connection handle. We do not know, therefore we need to plan carefully, or even better: wait for an actual case. Also, naming the callback http_something would be a misnomer. > I'll go ahead and submit another patchset using this approach to fix > the immediate segfault while we consider a larger API change. Thanks. It seems to me a very sane course of action, and I have no objection to the two patches you just sent. Regards, -- Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
