Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in
Toggle navigation
N
noVNC
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
rasky
noVNC
Commits
5ba1dd78
Commit
5ba1dd78
authored
Jul 02, 2010
by
Joel Martin
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
README/TODO: Windows browser testing results.
parent
2ca053af
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
29 additions
and
23 deletions
+29
-23
README.md
README.md
+26
-22
TODO
docs/TODO
+3
-1
No files found.
README.md
View file @
5ba1dd78
noVNC: HTML5 VNC Client
======================
## noVNC: HTML5 VNC Client
Description
-----------
### Description
noVNC is a VNC client implemented using HTML5 technologies,
specifically Canvas and WebSocket (supports 'wss://' encryption).
...
...
@@ -17,8 +15,7 @@ WebSocket SSL/TLS encryption, i.e. the "wss://" URI scheme.
(http://github.com/lyokato/as3crypto_patched).
Requirements
------------
### Requirements
Until there is VNC server support for WebSocket connections, you need
to use a WebSocket to TCP socket proxy. There is a python proxy
...
...
@@ -44,8 +41,7 @@ There a few reasons why a proxy is required:
sequence numbers to each packet.
Usage
-----
### Usage
*
To encrypt the traffic using the WebSocket 'wss://' URI scheme you
need to generate a certificate for the proxy to load. You can generate
...
...
@@ -79,27 +75,35 @@ Usage
button and enjoy!
Browser Support
---------------
### Browser Support
I only currently test under Linux. Here are the current results:
#### Linux (Ubuntu 9.04)
*
Chrome 5.0.375.29 beta: Works great. Native WebSockets support. Very
fast.
*
firefox 3.5: Works well. Large full-color images are slow mostly due
to flash WebSockets emulator overhead.
*
Chrome 5.0.375.29: Works great. Very fast. Native WebSockets.
*
Firefox 3.5: Works well. Large full-color images are slow mostly due
to web-socket-js overhead.
*
Opera 10.60: Works. Rendering performance is between firefox 3.5 and
Chrome. However flash WebSockets emulator interaction causes overall
performance to be lower than firefox 3.5 and causes occasional
hangs.
Chrome. However web-socket-js interaction causes overall performance
to be lower than firefox 3.5 and causes occasional hangs.
*
Arora 0.50: Works. Broken putImageData so large full-color images
are slow.
are slow.
Uses web-socket-js.
*
Konqueror 4.2.2: Broken:
flash WebSockets emulator
never loads.
*
Konqueror 4.2.2: Broken:
web-socket-js
never loads.
Integration
-----------
#### Windows (XP)
*
Chrome 5.0.375.99: Works great. Very fast. Native WebSockets.
*
Firefox 3.0.19: Works well. Some overhead from web-socket-js.
*
Safari 5.0: Works. Fast. Native WebSockets support. However 'wss://'
(SSL/TLS) does not work because client sends a strange handshake.
*
Internet Explorer 6, 7 and 8: Non-starter: not even basic Canvas
support.
### Integration
The client is designed to be easily integrated with existing web
structure and style.
...
...
docs/TODO
View file @
5ba1dd78
...
...
@@ -9,7 +9,9 @@ Short Term:
- Timing delta between frames in proxy record log, for playback
support (for demo and test).
- Track down hang in Opera after second disconnect.
- Opera hang after second disconnect.
- Opera event issues: keyboard not stopped. Middle mouse sticks.
Medium Term:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment