#11671: enable TCP keepalive socket options
-------------------------------------+-------------------------------------
Reporter: guest | Owner: (none)
Type: enhancement | Status: new
Priority: wish | Component:
| undetermined
Version: unspecified | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by MasterQuestionable):
͏ “The FFmpeg client receives data over an HTTP stream.
͏ But if the stream stops, for example: due to [https://ffmpeg.org
/ffmpeg-filters.html#silenceremove ͏"silenceremove"], or because a Suspend
and Resume occurred.
͏ And during that time, the remote side terminated the connection:
͏ The client will not detect that the connection has been lost after
the Resume, and will wait indefinitely.”
.
͏ You mean the HTTP connection won't automatically timeout..?
͏ Seems like strange behavior.
͏ The common behavior should be:
͏ Timeout if irresponding after certain period; then retry, of max
certain times.
͏ I'm unsure of FFmpeg's handling on network streams; which I never
counted on.
͏ “FF-* is not the appropriate networking tool.
͏ Though it did support some networking functionalities, for the
convenience.”
͏ Anyway I still find the TCP keepalive less reliable.
͏ In particular when used under its original intent: system-wide
enabled.
͏ A potential privacy risk.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11671#comment:4>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
