[
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16550839#comment-16550839
]
ASF GitHub Bot commented on CLOUDSTACK-10025:
---------------------------------------------
syed commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC
Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-406623411
Sorry guys, I have been pulled into various things and it's a challenge to
find time. I have to do this on my own time. I'll try to get to it this weekend.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> To create a better VNC client for Cloudstack using noVNC
> --------------------------------------------------------
>
> Key: CLOUDSTACK-10025
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10025
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VNC Proxy
> Affects Versions: 4.11.0.0
> Reporter: Sachin
> Priority: Minor
> Labels: features
>
> I have implemented this feature as my GSoC'17 project. noVNC is written in
> javascript and uses websockets to connect to VNC server. We have modified the
> ConsoleProxy server to accept websocket request from noVNC client, which then
> forwards the request request to VNC server.
> Javascript cannot make plain tcp request, hence the websocket request have to
> be forwarded to the VNC server via a proxy server that basically converts
> websocket request from client to plain tcp request for VNC server.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
