> Client controls compression in both directions, not separately in/out. > Must say that in most cases (i.e. LAN) compression makes almost no > visible effect regarding both data exchange speed (network is too fast) > and CPU load (compression of relatively small data volume, passed over > the wire, is not a problem for today CPU). Just in order to avoid > unneeded actions it's turned off by default. Another case is low speed > connection. Here is absolutely no need in saving CPU, and both streams
Fully agree. > are compressed. I can't imagine a case where it creates problems, and > therefore separate in/out setup looks just like unneeded complication > for both protocol and user environment. So how do I know whether I should or shouldn't (de)compress the network stream? -- Mgr. Jiří Činčura Independent IT Specialist ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
