jcarr
/
noVNC
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Clarify browser results in README.md

This commit is contained in:
Joel Martin 2010-07-01 12:18:18 -05:00
parent a94699265e
commit e091b47a9f
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@ -86,15 +86,16 @@ I only currently test under Linux. Here are the current results:
* Chrome 5.0.375.29 beta: Works great. Native WebSockets support. Very * Chrome 5.0.375.29 beta: Works great. Native WebSockets support. Very
fast. fast.
* firefox 3.5, 3.7: Works well. Large full-color images are slow * firefox 3.5: Works well. Large full-color images are slow mostly due
mostly due to flash WebSockets emulator overhead. to flash WebSockets emulator overhead.
* Opera 10.60: Works. Rendering performance between firefox 3.5 and * Opera 10.60: Works. Rendering performance is between firefox 3.5 and
Chrome. However, flash WebSockets emulator interaction causes Chrome. However flash WebSockets emulator interaction causes overall
inconsistence overall performance and occasional hangs. performance to be lower than firefox 3.5 and causes occasional
hangs.
* Arora 0.50: Works. Broken putImageData so large full-color images * Arora 0.50: Works. Broken putImageData so large full-color images
are slow. are slow.
* Konqueror 4.2.2: Broken: flash WebSockets emulator never connects. * Konqueror 4.2.2: Broken: flash WebSockets emulator never loads.
Integration Integration