On 05/25/2016 08:42 PM, Jiří Činčura wrote: >> 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? >
Decision to use compressed or not compressed connection is done by client, i.e. by you :) That has a good reasoning - only client knows is it connected to server via slow line. That means that if your client does not support compression at all that will never become a reason of any connection failure - you will simply not request it. Network redirector in fbclient decides to use compressed connection based on config value WireCompression. If your client supports std config it can also use it. If not - hmm, you will have to invite something else to let people use compression. A. PS. Sorry for late answer. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
