On Mon, 25 Sep 2006 00:45:34 +0100, Richard June <[EMAIL PROTECTED]> wrote:
> Then I completely misunderstood the purpose of Xdamage. I thought it would > transmit only the parts of the page which had changed, no matter the reason. If this where the case - for video - most pixels will change from frame to frame anyway (think about motion tracking codecs for example) and computing the difference between successive frames would be very processor intensive, as would applying the diffs at the other end. The only way I can see round this would be to pass the video to clients compressed and have it uncompressed there. There would be lots of ways to do this, like passing the video file in whatever format it happened to be in over to the client for display. I have really wanted to run VLC as a local app for this purpose, but not got round to it. There's a short Xdamage summary here: http://freedesktop.org/wiki/Software/XDamage -- From Ben Green ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
