l chosen command name is
> unlikely
> to conflict with (and therefore can be used in concert with) any other
> protocol
> extensions.
>
We thought about it, and it seemed more logical to add it as a packet type
since it was affecting the RTMP connections itself. If you read the
definit
Nowadays when you are streaming to a live platform if the RTMP(s)
server needs to restarted for any reason (ex: deploy new version)
the RTMP connection is interrupted (probably after some draining time).
Facebook will publish a proposal to avoid that by sending a
GoAway message in the RTMP protocol
Nowadays when you are streaming to a live platform if the RTMP(s)
server needs to restarted for any reason (ex: deploy new version)
the RTMP connection is interrupted (probably after some draining time).
Facebook will publish a proposal to avoid that by sending a
GoAway message in the RTMP protocol
Nowadays when you are streaming to a live platform if the RTMP(s)
server needs to restarted for any reason (ex: deploy new version)
the RTMP connection is interrupted (probably after some draining time).
Facebook will publish a proposal to avoid that by sending a
GoAway message in the RTMP protocol
Nowadays when you are streaming to a live platform if the RTMP(s)
server needs to restarted for any reason (ex: deploy new version)
the RTMP connection is interrupted (probably after some draining time).
Facebook will publish a proposal to avoid that by sending a
GoAway message in the RTMP protocol
Thanks!
Will do
Jordi
On Mon, Jan 23, 2017 at 10:36 AM, wm4 wrote:
> On Sun, 22 Jan 2017 20:31:36 +0100
> Jordi Cenzano wrote:
>
> > Hi, I'm and old user of ffmpeg but I'm new in this community. So first of
> > all let me congrat you for your work, ffmpeg has b
read SMPTE time
code).
Since this is NOT a patch I don't know which is the best way to submit my
changes for review, for now I created this PR against a FFmpeg forked repo:
https://github.com/jordicenzano/FFmpeg/pull/1
It woud be great some guidance on that
