#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):

 ͏    All linked contents are adequately verified. (specifically for the
 anchored portion)
 ͏    Maybe it's somehow tagged Java-related.
 ͏    But the concept (of TCP keepalive in general) applies generally.
 ͏    .
 ͏    The 1st link is primarily intended to provide context, on what TCP
 keepalive is.
 ͏    And the anchored answer
 ([https://stackoverflow.com/questions/1480236/does-a-tcp-socket-
 connection-have-a-keep-alive#33927447 #33927447]) is clearly not much
 Java-related.
 ͏    (more likely a description of TCP keepalive in general)

 ͏    As for "TCP_KEEPALIVE", I'm unsure if it's certain FFmpeg specific
 thing.
 ͏    (rough search of FFmpeg source didn't give much meaningful hint)
 ͏    But caveat the behavior I describe:
 ͏    Though similar, it's not exactly TCP keepalive. (fundamentally
 differs in many details)

 \\
 ͏    On the privacy concerns, it's mostly about the periodic ping alike.
 ͏    At times can be undesirable. (unintended network traffic)
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11671#comment:7>
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".

Reply via email to