title: Does DeflateStream "skip" decompression if the data was not originally compressed?
body: <p>I'm not familiar with the internals of DeflateStream, but I need to store files in a Vendor's DB system that uses DeflateStream on binary attachments. The first thing I noticed was that all of my files were 10-50% BIGGER after compression, but I attribute that to a less sophisticated compression algo on top of files that are already highly compressed (in this case they were all PDFs). My question however relates to the fact that when I just wrote the original file into the BLOB the Vendor's application had no problem opening it (it opened the attachments I compressed with deflate as well). Is there a header on the compressed data that tells DeflateStream that the data's not compressed and basically pass it on as-is? <a href="http://datatracker.ietf.org/doc/rfc1951/" rel="nofollow">This</a> is the specification; can anyone familiar with it point where this is defined - or am I off base and the vendor is doing some magic behind the scenes?</p>