Commit b8e07362 authored by Joel Martin's avatar Joel Martin

A little more cleanup of browser table.

parent 3df41d67
...@@ -91,22 +91,20 @@ In the following table Jaunty is Ubuntu 9.04 and WinXP is Windows XP. ...@@ -91,22 +91,20 @@ In the following table Jaunty is Ubuntu 9.04 and WinXP is Windows XP.
<td>Excellent</td> <td>Excellent</td>
<td>Very fast. Native WebSockets.</td> <td>Very fast. Native WebSockets.</td>
</tr> <tr> </tr> <tr>
<td>Jaunty</td> <td> Firefox 3.5</td> <td>Jaunty</td> <td>Firefox 3.5</td>
<td>Good</td> <td>Good</td>
<td>Large full-color images are somewhat slow due to <td>Large full-color images are somewhat slow from web-socket-js overhead.</td>
web-socket-js overhead.</td>
</tr> <tr> </tr> <tr>
<td>Jaunty</td> <td> Opera 10.60</td> <td>Jaunty</td> <td>Opera 10.60</td>
<td>Fair</td> <td>Poor</td>
<td>web-socket-js interaction problems: slower than firefox, <td>web-socket-js problems, mouse/keyboard issues. See note 1</td>
occasional hangs.</td>
</tr> <tr> </tr> <tr>
<td>Jaunty</td> <td> Arora 0.5</td> <td>Jaunty</td> <td>Arora 0.5</td>
<td>Good</td> <td>Good</td>
<td>Broken putImageData so large full-color images <td>Broken putImageData so large full-color images
are slow. Uses web-socket-js.</td> are slow. Uses web-socket-js.</td>
</tr> <tr> </tr> <tr>
<td>Jaunty</td> <td> Konqueror 4.2.2</td> <td>Jaunty</td> <td>Konqueror 4.2.2</td>
<td><strong>Broken</strong></td> <td><strong>Broken</strong></td>
<td>web-socket-js never loads</td> <td>web-socket-js never loads</td>
</tr> <tr> </tr> <tr>
...@@ -115,26 +113,33 @@ In the following table Jaunty is Ubuntu 9.04 and WinXP is Windows XP. ...@@ -115,26 +113,33 @@ In the following table Jaunty is Ubuntu 9.04 and WinXP is Windows XP.
<td></td> <td></td>
<td></td> <td></td>
</tr> <tr> </tr> <tr>
<td>WinXP</td> <td> Chrome 5.0.375.99</td> <td>WinXP</td> <td>Chrome 5.0.375.99</td>
<td>Excellent</td> <td>Excellent</td>
<td>Very fast. Native WebSockets.</td> <td>Very fast. Native WebSockets.</td>
</tr> <tr> </tr> <tr>
<td>WinXP</td> <td> Firefox 3.0.19</td> <td>WinXP</td> <td>Firefox 3.0.19</td>
<td>Good</td> <td>Good</td>
<td>Some overhead from web-socket-js.</td> <td>Some overhead from web-socket-js.</td>
</tr> <tr> </tr> <tr>
<td>WinXP</td> <td> Safari 5.0</td> <td>WinXP</td> <td>Safari 5.0</td>
<td>Fair</td> <td>Fair</td>
<td>Fast. Native WebSockets. Broken 'wss://' <td>Fast. Native WebSockets. Broken 'wss://' (SSL) - weird client header</td>
(SSL) - weird client header</td>
</tr> <tr> </tr> <tr>
<td>WinXP</td> <td> IE 6, 7, 8</td> <td>WinXP</td> <td>IE 6, 7, 8</td>
<td><strong>Non-starter</strong></td> <td><strong>Non-starter</strong></td>
<td>No basic Canvas support. Javascript painfully slow.</td> <td>No basic Canvas support. Javascript painfully slow.</td>
</tr> </tr>
</table> </table>
* Note 1: Opera interacts poorly with web-socket-js. After two
disconnects the browser tab or Flash often hang. Although Javascript
is faster than Firefox 3.5, the high variability of web-socket-js
performance results in overall performance being lower. Middle mouse
clicks and keyboard events need some work to work properly under
Opera.
### Integration ### Integration
The client is designed to be easily integrated with existing web The client is designed to be easily integrated with existing web
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment