On 12/4/14 10:41 AM, Dyweni - TurboVNC-Users wrote: > How about WebSockets? Do you see any potential issues with this? > > 1. TurboVNC Applet modifications > > Modify TurboVNC Applet to connect using encrypted WebSockets > (wss://). > > 2. Apache 2.4 + mod_proxy_wstunnel > (http://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html) > > This would proxy the wss:// connection received at the webserver > to a backend websocket server. > > 3. Websockify > (https://github.com/kanaka/websockify) > > This would proxy the data between the websocket connection and the > actual VNC server.
The issue is that TurboVNC doesn't speak the WebSockets protocol. Bear in mind that there are two connections we're dealing with: the first is the connection to the web server to download the applet. The second is the RFB connection from the applet to the VNC server. Since each VNC server instance listens on a different port, you would need a server-side proxy that is smart enough to take connections on a single port and farm them out to multiple VNC server instances, each sitting on a different port. UltraVNC Repeater, for instance, can do that, but since it speaks the RFB protocol, no modifications are required to the viewer in order to use it. Not sure why you couldn't just use SSH tunneling, which is built into the Java viewer. That is a single-port solution and gives you encryption to boot. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ TurboVNC-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/turbovnc-users
