Hi Julius,
> <
https://www.ibm.com/docs/en/i/7.3?topic=support-using-vncviewer-web-browser>
That document is referring to RealVNC, which (while sharing a common
ancestor a long time ago) is a different thing. RealVNC is not open
source and neither is their protocol, it's a paid product. It's
impossible for projects like noVNC to be compatible with RealVNC. And
they don't have any interest in being compatible with open source
clients like us.
While we can't know for sure, my guess is that RealVNC's server has a
built-in WebSocket proxy, just like the one we're talking about here.
> And why in general can web browsers not do this?
It's not about VNC, it's about communication with a regular TCP service.
Browsers are built to be mostly cut off from the local system, it's
often referred to as a sandboxed environment. Just imagine that a script
somewhere on the internet gets loaded into the browser and could from
inside the browser access every computer reachable by the browser with
arbitrary protocols. It's as a safety barrier.
> Why not just include the VNC package in their internal libraries?
>
> I mean why Firefox, Chrome, etc don’t build this in.
You have Chrome Remote Desktop, perhaps that's what you're looking for?
Plugins or extensions in the browser likely has fewer restrictions, but
that means you're loosing one of the main advantages of a web
application - the users will have to install something.