Hello everybody, I am just getting started with WCS5 and my goal is to port an existing application that uses a different media server that we have grown very unsatisfied with to WCS5 to see if it performs better.
The current application allows users to connect to several IP cams, it is split into 3 separate parts: the client (html5 website), the media server that serves the RTSP stream of the IP cams to the clients with WebRTC and a Node.js app in the middle that handles the logic of checking if the users are allowed to see those streams, handle all the handshakes and DB logic, etc.
The way it works is the client sends a request to the node app via websockets asking to view a specific IP cam, then the node app talks to the media server handling all the SDP offer/answer logic, etc and sends back to the client the stream of the IP cam.
Now going through the examples and docs of WCS5, using the "Player" demo i can successfully connect to one of those IP cams and i get the stream properly. So far so good.
But as far as i can tell, the flashphoner client communicates directly with the media server, meaning the full URL of WSC5 as well as of the IP cam is visible (including its username/password) to the users and I can't do extra processing. I've been searching through this forum and found this link that seems to address (partly) this subject. From what I understand from that thread, one way to solve this would be to make an EchoApp that responds to certain REST calls and do my custom processing in there, is that correct? Or can i use the approach of my current system and simply have a Node.js app that communicates directly with WCS5 to create/stop the streaming of the IP Cam and simply sends back to the client (browser) the stream?
I hope my question is not too confusing, any help appreciated!
The current application allows users to connect to several IP cams, it is split into 3 separate parts: the client (html5 website), the media server that serves the RTSP stream of the IP cams to the clients with WebRTC and a Node.js app in the middle that handles the logic of checking if the users are allowed to see those streams, handle all the handshakes and DB logic, etc.
The way it works is the client sends a request to the node app via websockets asking to view a specific IP cam, then the node app talks to the media server handling all the SDP offer/answer logic, etc and sends back to the client the stream of the IP cam.
Now going through the examples and docs of WCS5, using the "Player" demo i can successfully connect to one of those IP cams and i get the stream properly. So far so good.
But as far as i can tell, the flashphoner client communicates directly with the media server, meaning the full URL of WSC5 as well as of the IP cam is visible (including its username/password) to the users and I can't do extra processing. I've been searching through this forum and found this link that seems to address (partly) this subject. From what I understand from that thread, one way to solve this would be to make an EchoApp that responds to certain REST calls and do my custom processing in there, is that correct? Or can i use the approach of my current system and simply have a Node.js app that communicates directly with WCS5 to create/stop the streaming of the IP Cam and simply sends back to the client (browser) the stream?
I hope my question is not too confusing, any help appreciated!