GitHub/noVNC
1
0
Fork 0
mirror of https://github.com/novnc/noVNC.git synced 2026-06-08 13:24:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update firefox 4.0 support. Misc perf notes updates.

Joel Martin
2011-03-21 16:34:12 -05:00
parent 1e8a0bb323
commit 4ab1998aac
2 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Browser-support.md

@@ -20,9 +20,9 @@ This list show results of testing noVNC on various browser and OS combinations.
<td>Excellent</td>
<td>Very fast. Native WebSockets.</td>
</tr> <tr>
<td>Firefox 4.0 Beta 9</td>
<td>Firefox 4.0</td>
<td>Good</td>
<td>Native WebSockets must be turned on (see note 4)</td>
<td>Very good with native WebSockets enabled (see note 4)</td>
</tr> <tr>
<td>Firefox 4.0 Beta 6</td>
<td>Excellent</td>

10
Performance-notes.md

@@ -76,10 +76,14 @@ direction to go in this area.
### tight encoding
Of the normal RFB encodings noVNC supports "raw", "copyrect", "RRE"
and "hextile". The "hextile" encoding is much more bandwidth efficient
than "raw" or "RRE" but it is still not nearly as efficient as some of
the other zlib based encodings: "zlib", "ZRLE", and "tight".
I briefly explored implementing the "tight" encoding in noVNC but
quickly discovered that tight uses zlib to compress the lossless pixel
data in the stream. Decompressing zlib in Javascript is relatively
slow so I gave up on that route.
tight uses zlib compression and decompressing zlib directly in
Javascript is relatively slow so I gave up on that route.
However, there might be a way to trick the browser into doing zlib
decompression in native code instead of Javascript. Tobias Schneider