-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > My fault for only just joining in etc, but why have the underlying > Tar/Zip classes become package scoped? Does the bridging API replace > all need to dig into the lower-level APIs? >
I was not thinking enough about this. In my fault i was thinking its a good idea to lower visibility. But i didn't think about if the bridge has enough functionallity or not. > If so, why are the bzip classes still public? Cause bzip still needs refactoring. There were compile errors on severeal points, and i didn't want to dig all up. > Should there be ZipCompressor and GZipCompressor implementations? In my opinion, yes. > Any reason for there not being an archiveToStream method? Especially > in the case of the Tar implementation where you'd want to attach a > TarArchiver to a GZipCompressor. I don't know any reason not to do so. I will remind this in Draft 6. Thanks, Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEVymhkv8rKBUE/T4RAk0yAJ9Jx6+pfSRVvsuApFCbZpkKiO7AwQCeJPLx g3rJSBX+ovIEPZrW7JKJnLY= =YsaR -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
