of seen bytes.
… to allow specifying a concrete BufferRecycler instance, as an alternative to the default ThreadLocal soft-references policy. The change does not break compatibility with existing API, but adds flexibility for resource-eficiency if used from pools (different threads could reuse the same BufferRecycler instances, avoiding the creation of instances on a per Thread basis) and some minor performance gain in preexistent LZFOutputStream constructors (because ThreadLocal is only accessed once).
DeflaterOutputStream internally holds a reference to the Deflater. Writing to the stream after calling close thus silently corrupts the Deflater. This causes data breech between two consecutive user of the same Deflater instance. This fix would cause error in what obviously a erroneous use of the stream instead of silent corruption.