For implementations that don't care about memory efficiency, you're right that they'll unencode the huffman-encoded strings. :) The majority of non-efficiency-oriented APIs I've used treated the overhead of HTTP and IO as insignificant, and likely just wouldn't care about this at all. -=R On Fri, May 10, 2013 at 8:01 PM, Martin Thomson <martin.thomson@gmail.com>wrote: > On 10 May 2013 18:30, Roberto Peon <grmocg@gmail.com> wrote: > > The memory needed for header interpretation will, for a decent > > implementation, be at worst the sum of the size of the compression > context > > and the size of the receive buffer-- it will not expand once decompressed > > unless a lot of useless copying is being done. > > I was going to say the same thing until I realized that most APIs will > be forced to decode Huffman-encoded strings to present. Some > implementations might avoid this entirely, others might defer > decompression, or something along those lines, but there is probably > going to be at least some exposure to the decompressed data. >
Received on Saturday, 11 May 2013 03:16:21 UTC