My best guess is that it would increase the minimum requirements of Yawcam a lot and would make configuring Yawcam complex. Of course Malun has better knowledge about how big the operation would become.
So if you were to have multiple cameras streaming data to one single port, it would need a complete rewrite of the internal web server code and/or terrifying modifications to the Java Applet and the handling of multiple streams at once. So if you have a web server already running on the port, the companion program would run, but would do nothing. If there is a program, that has already taken the port, a second program can't take it. Only one program at a time can take the "ownership" of the port. The other problem is the reservation of ports. By my best knowledge, Malun would have to write a completely new and own protocol for Yawcam, so that it would work. Since every communication with Yawcam's web server is always started by sending a HTTP request, it is quite impossible to have a third party program see if the request was for the a webcam. A HTTP request is always sent first to make contact with Yawcam's internal web server and after that, Javascripts start up, because the internal web server is programmed to do so. Only Javascript seems to make the difference in communication. The Webcam and HTTP requests are practically the same thing. All that will actually show in repetier is 3 x Webcams and it seems to alternate between the 1 webcam that isnt working, wont show and another. I have 2 x Prusa MK3S MMU2 Printers both with 2 x Webcams each.
REPETIER SERVER WEBCAM PRO
Sounds plausible in theory, but in practice, things get more complicated. Im struggling to get multiple webcams running on my Repetier Server Pro 1.0.4 It seems the max repetier will let me have is 3 webcams total. But if you made a third program running on port 80, that program checked if it was webcam or http request and then sent the request to the right program
0 kommentar(er)
