I just read about this.<br><br>Google has introduced and open sourced  a new image format to help speed up
 the performance of websites called W<b>ebP</b>.<br><ul><li><b>WebP has a 40% improvement over JPEG and WebP was designed to improve the compression offered by JPEG</b>.</li><li>Google has 
<a href="http://code.google.com/speed/webp/gallery.html" target="_blank">created a site</a>
 for Web developers and users to assess the performance of WebP. <br></li><ul><li>The 
images presented at the site show WebP side-by-side with JPEG images. 
The WebP images are 40 to 50 percent trimmer in bytes but look the same 
to the human eye. <br></li><li><b>WebP is based on Google&#39;s VP8 codec that they also open-sourced recently.  </b> VP8 is part of the heart of HTML 5&#39;s video capability.</li><li>

To trim down file size for WebP, Google used an image compressor based 
on the VP8 codec that Google open-sourced in May 2010.<br></li></ul></ul>


My question for x2go developers is <br><br>                             Could WebP (or VP8 codec itself) be implemented at both the x2go-server and the x2go-client and <i><b>possibly get a substantial improvement</b></i> in video performance ??<br>
<br>Currently x2go as most NX oriented solutions (Freenx, NoMachine NX) typically use JPEG for compression.     <br><br>But it seems to me that WebP could be implemented and as it is reported to be 40% more efficient than JPEG...  <br>
<br>                            less bytes means less network traffic and usually better/faster performance.<br><br><br>Brian Mullan<br><br>