tanonl commented on PR #624: URL: https://github.com/apache/guacamole-server/pull/624#issuecomment-3612993343
> This is a solid and much-needed feature for remote users! The protocol-agnostic video handler infrastructure in the core library makes future camera/video streaming features much more maintainable across other protocols (e.g., VNC, SSH, etc.). Great to see that the pattern mirrors the audio handler work. Out of curiosity, do you foresee any unique challenges if/when adapting the video handler for non-H.264 codecs or non-RDP protocols Hi @Shankhadeep1234, thank you for the positive feedback! I'm glad the protocol-agnostic design resonates with you. For your question, I think the main challenges would be: -- browser codec support - H.264 has universal MediaRecorder support and hardware encoding, while VP8/VP9/AV1 vary significantly across browsers and may struggle with real-time encoding on older devices, -- protocol specs - The current RDPECAM implementation benefits from well-defined capability structures in the MS-RDPECAM spec, VNC has no official camera redirection standard so we'd need a custom RFB extension -- and SSH would likely require tunneling as separate forwarded channels rather than protocol integration. At least, the video_handler infrastructure and CameraRecorder.js are already codec/protocol-agnostic, so the heavy lifting is reusable - each other protocol mainly needs capability negotiation and a transport bridge layer. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
