Support for TCP transport (interleaving)

[maslowalex]

Hi! Thank you for a great library!

I'm interested in adding the support for TCP transport and I wanted to ask for your support to not spend much time refactoring the code.

Could you elaborate on your vision, maybe with the changes required to make this happen. This would help me spend less time on refactoring / aligning the code with your vision.

Looking forward to your input @gBillal 🙏

[gBillal]

@maslowalex just to be sure, we are talking about tcp support for record method ?

[maslowalex]

@maslowalex just to be sure, we are talking about tcp support for record method ?

Absolutely. Also known as push approach.

[gBillal]

I think there's two issues that needs to be addressed

• When a user is recording using tcp, the server should not attempt to read from the socket. A field recording? in the client connection may be sufficient to handle this case.
• The second issue is to forward rtsp messages by the handler to the server. We can use a simple send(conn_pid, {:rtsp_message, message}) and handle it. I wonder if there's a better api to expose for this use case. The pid can be retrieved easily in the handler by using self().