Re^3: Optimizing TCP packet usage with IO::Socket::INET or similar

o.k., folks, Your replies make my life much easier, because I do not have to code anything regarding tcp packet stuffing. I will leave it up to the geniuses who brought TCP to us.

But: Does somebody know anything about the compression issue?

Is it like that, that when I send the data compressed to the socket using Net::EasyTCP, the application on the remote side is responsible for decompressing (i.e., the client cannot "trigger" this). Might seem to be a silly question, but, honestly, I am not a genuine network programmer. ;-)

Comment on Re^3: Optimizing TCP packet usage with IO::Socket::INET or similar

Replies are listed 'Best First'.
Re^4: Optimizing TCP packet usage with IO::Socket::INET or similar by BrowserUk (Patriarch) on Oct 06, 2016 at 15:46 UTC
the application on the remote side is responsible for decompressing (i.e., the client cannot "trigger" this). Absolutely! tcp conveys packets of data from A to B; it neither knows nor cares whether what inside those packets is compressed or not. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :) In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]
Re^4: Optimizing TCP packet usage with IO::Socket::INET or similar by talexb (Chancellor) on Oct 11, 2016 at 15:45 UTC
Once again, do a benchmark and find out whether compression makes a difference. You can only do so much thinking -- eventually you have to climb the tree. :) Alex / talexb / Toronto Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.	[reply]