(Cross-posting to both tigervnc-devel and rfbproto as this is a general protocol issue, but tigervnc will be the playground for testing it)
Hi, I'm looking at making VNC/RFB work better over high latency network. Right now we're limited to one update per RTT, which makes things rather unpleasant over many links. Things are still very much up in the air, but I've written down my thoughts so far and I'd appreciate any input you could give on it. You can find my notes here: https://sourceforge.net/apps/mediawiki/tigervnc/index.php?title=VNC_Latency_Considerations Rgds -- Pierre Ossman OpenSource-based Thin Client Technology System Developer Telephone: +46-13-21 46 00 Cendio AB Web: http://www.cendio.com A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________ tigervnc-rfbproto mailing list tigervnc-rfbproto@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-rfbproto
