>>If you go that way, please use the HTTPServer class, so that we get a fully >>async implementation.
maybe this could help: http://search.cpan.org/~vti/Protocol-WebSocket-0.17/ https://github.com/vti/protocol-websocket/blob/master/examples/anyevent-http-server.pl >>But first I would really like to have a simple prototype (using wsproxy) to >>play around. I can take time next week to test too. ----- Mail original ----- De: "Dietmar Maurer" <diet...@proxmox.com> À: "Stefan Priebe - Profihost AG" <s.pri...@profihost.ag>, "Alexandre DERUMIER" <aderum...@odiso.com> Cc: pve-devel@pve.proxmox.com Envoyé: Dimanche 1 Juin 2014 15:22:28 Objet: RE: [pve-devel] preview of novnc integration ready > > But that mean too that each vm need to listen on 1 tcp port to handle vnc > connection. > > (I think a proxy + qemu on unix socket is better in this case) > > Yes. I'll try to port the wsproxy.py to perl. If you go that way, please use the HTTPServer class, so that we get a fully async implementation. But first I would really like to have a simple prototype (using wsproxy) to play around. I can take time next week to test. _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
