In early versions compression was done 'on-the-fly' by a [http.ResponseWriter] wrapper.
This was bad because it was not possible to for the [http.ServeContent] function to determine
and set the Content-Length header to the response.
Not setting the Content-Length header cause all sorts of problems, like being unable to serve
Range requests, enabling connection reuses, etc.
For now, the server only compresses files that are less than 15mbs in length, since it's done in memory,
and should cover most assets normally served in a web application.
Full Changelog: v0.6.0...v0.6.1