Adam Tkac wrote: > You know colorspace code well so decide what is the best approach. If > that code is quite risky then revert it. But if that code is > not so risky you can leave it as in r3759 even there is no big > performance improvement. > > I think you could tune defer updates directly in > unix/xserver/hw/vnc/XserverDesktop.cc instead of in vncserver. Also > update Xvnc manual page, please. > > Thanks for your detailed inspection, it's really helpful. > There is no risk in the new code, really. It just requires a bit more memory, but I think in the long term it will prove to be beneficial, and it will be necessary once we implement Pierre's idea of passing the PixelBuffer directly into the encoder. Thus, I'll leave it in.
------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
