> > please ping this thread when this happens > > about the patch itself > > IIUC a user using old rtmpdump with new ffmpeg would loose the > rtmp_buffer_size option. > Would it make sense to support the old setsockopt() code for this > case ? > > [...] > > > That's a really good point. So the only real question then is whether to keep it the way it is, or to submit another patch to support the other two options (which are not as important IMO) in the same manner as Brian's patch. Either way, it would eliminate the dependency on rtmpdump. What do you think?
Thanks, Cary _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
