-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate websockify into cherrypy #22
Comments
I wander if I can take this one? |
Sure... I will assign it to you. |
@lvroyce, this issue is pending on 5 months. please fix it ASAP. |
duplicate with issue 90 |
Issue #90 is about using a single instance of websockify to handle all kimchi connections (instead of create one instance per connection) And this issue is about incorporate websockify into cherrypy that way we can eliminate the use of websockify script. |
@wudx05 any comments? |
I don't see any other benefits to incorporate websockify into cherrypy. Aline, could you please elaborate why we need incorporate websockify into cherrypy? IMO, we can close this issue |
This already fixed by Markwu. |
@wudx05 As proposed by Adam, integrating websockify into cherrypy can eliminate the need of manage and clean up the spawned websockify processes. |
Kimchi does not launch an external process for websockify anymore. |
noVNC is supported in Kimchi by launching an external program (websockify.py) to wrap an existing qemu vnc connection with web sockets (needed by noVNC). This works but has a number of disadvantages:
Anthony proposed an idea to support websocket proxying directly from the cherrypy server on its given port. The noVNC code would be directed to a URL such as: ws://:8000/vms/vm-1/vnc. Cherrypy would switch to a websockets handler to service connections at this URL.
The text was updated successfully, but these errors were encountered: