Can you explain what all of the "fence" stuff is doing? Also, why is there both a CU message (which uses the registered number of 150) and a CU pseudo-encoding?
On 11/9/11 3:41 AM, Pierre Ossman wrote: > Here is the promised patch to "fix" the latency issue in VNC. The basic > idea is to let the server start sending updates without requests, but > doing so in a way that doesn't overload the client or the network. > > WARNING! This patch uses protocol numbers that aren't properly > registered and should therefore not be deployed anywhere! > > Rgds > > > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > > > > _______________________________________________ > Tigervnc-devel mailing list > Tigervnc-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tigervnc-devel ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
