Difficulty is that the clipboard knows nothing about compression feature availability, as it is not directly tied to a client connection, at least on the server. When a new client comes in, we just hand over the clipboard instance...
Also, it does not have access to the per-client encoding thread, which would be the ideal place for slotting the compression work...
Groundwork done in r7041, we no longer assume
self.damage_data_queue(which should be renamed as compression queue or something more generic), or using a wrapper telling the network encode layer to do it
Some ugly code remains in
compressed_wrapper calls, but that is now well isolated and can be dealt with later.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/621