On Mon, Feb 23, 2015 at 10:28:29PM -0600, Cary Tetrick wrote:
> >
> > 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()
>
> 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
On Wed, Feb 11, 2015 at 07:33:43PM -0600, Cary Tetrick wrote:
> This reimplements a change authored by Brian Brice
> 2015-01-19
> "librtmp: Allow changing the socket send buffer size"
> (Brian is aware of this change).
> also negates change by Michael Niedermayer 2015-01-23
> 10:45:35
> "avforma
This reimplements a change authored by Brian Brice
2015-01-19
"librtmp: Allow changing the socket send buffer size"
(Brian is aware of this change).
also negates change by Michael Niedermayer 2015-01-23
10:45:35
"avformat/librtmp: Fix build with --disable-network --enable-librtmp"
because it is
