Experiment with compression #53
Description
SharpRemote's new binary protocol should allow for messages to be compressed.
The protocol should allow for individual messages to be compressed on-demand (for example when a certain size or entropy is exceeded). Ideally, a user should not have to decide whether or not messages are encrypted and then suffer the consequences of it, but instead SharpRemote should make a decision which satisfies 90% of users, striking the right balance between additional CPU/Memory requirements and bandwidth.
If compression happens to significantly reduce the required bandwidth of real world scenarios without increasing the required cpu time / memory by too much, then compression should be enabled by default. Opting out of using compression should be possible, however.