HTTP: Should keep connection when unpublishing. When the streaming is disconnected, FLV playback is also stopped, while RTMP continues playing, resulting in inconsistent behavior.

[jinleileiking]

The current logic I see is to wait for the client to disconnect the RTMP streaming link. The logic for HTTP-FLV is for the SRS server to actively disconnect. Can we make this consistent?

In FLV streaming, this feature exists, but it is not available in RTMP streaming.

TRANS_BY_GPT3

[winlinvip]

This is a problem that should be consistent.

If there is no disconnection, the client will not be aware when the anchor starts streaming again, which provides a better user experience.

However, FLV is difficult to maintain because it requires deleting the HTTP mount.

Of course, sometimes RTMP also needs to be disconnected in order to save resources.

So I think the better solution is: when RTMP configuration is disconnected for streaming, whether to also disconnect the playback, the default is to not disconnect and keep it consistent with the current situation.

I have marked this issue as good first issue, and everyone is welcome to provide a patch.

TRANS_BY_GPT3

[tangrufeng]

This is a problem, it should be consistent.

If there is no disconnection, the client will not be aware when the anchor starts streaming again, which provides a better user experience.

However, FLV is difficult to maintain because it requires deleting the HTTP mount.

Of course, sometimes RTMP also needs to be disconnected in order to save resources.

So I think the better solution is: when RTMP configuration is disconnected for streaming, whether to also disconnect for playback, the default is to not disconnect and keep it consistent with the current setting.

I have marked this issue as good first issue, and everyone is welcome to provide patches.

Yes, I also expect that the streaming end can be disconnected while the HTTP end remains in a normal connected state, instead of EOF.

TRANS_BY_GPT3