- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
Sbaz and pack200?
Mon, 2009-08-24, 02:23
I was wondering what people think about optionally using pack200 within the SBP distribution files used by sbaz? I have bigger fish to fry at the moment, but have been milling over this as a feature to reduce bandwidth usage and download times. The only reason why I'm hesitant is I very rarely see it being used (only Sun's JVM installer) and the resulting unpacked JAR will be different than the original JAR created (ordering of content per the documentation... if I remember correctly). I'm guessing the apparently infrequent use in the wild is partly due to supporting pre 1.5 JVM versions. Scala 2.8.0 will only be supporting 1.5+, thus making the 1.5 version dependency a non-issue. Is this correct? Has anyone run into problems with pack200 or heard of any corruption problems with the compression?
To give an idea on the potential savings, I applied pac200 to a nightly build of the scala-compiler.jar file. It reduced from 7.2MB to 2.0MB using the default compression of 5 and 1.9MB with a compression of value of 9. It would probably be implemente such that a contained JAR file would simply be extracted as it currently is, but a PACK.GZ file would always be unpacked into a JAR file.
To give an idea on the potential savings, I applied pac200 to a nightly build of the scala-compiler.jar file. It reduced from 7.2MB to 2.0MB using the default compression of 5 and 1.9MB with a compression of value of 9. It would probably be implemente such that a contained JAR file would simply be extracted as it currently is, but a PACK.GZ file would always be unpacked into a JAR file.