 Re: save client data with rtmpsuck
I mean the whole communication. Exact copy (bytes) of what the client sends to the server and also the rtmp url.
Some websites have implemented their own "protocol". They send additional data that the client needs to respond to first or they won't send the stream. For these websites you need to use rtmpsuck. I'm doing some experiments and it seems that when you create a new connection and send the exact same bytes to the server (mimicking the data exchange), then you can trick some servers into sending the stream. This way I might be able to write a tool that can save multiple streams without having to keep a browser tab open for each stream.
|