whit3

You're right. `ServeFiles` doesn't give you access to the `http.ResponseWriter` for setting his headers. It would be nice to have a third parameter (like `maxAge uint32`) for `ServeFiles` to set...

A `ServeFiles`-like function is only used for serving files directly from the provided `http.Dir` so: - This function already writes in the `http.ResponseWriter`'s body : a whole access to it...

We all know there are **a lot** of different file serving situations: - cache strategies - GZIP - minification - compilation (CoffeeScript, SASS, template languages…) - on-the-fly image resizing -...

A patched `ServeFiles` seems like a good idea: ``` go func ServeFiles(path string, root http.FileSystem, filter ...Handle) ``` But could you explain where do you write the response body? 'Cause...

OK, I see. But my proposal was to just embed gzipping (and cache headers) inside the _httprouter_ package. And for that, there is no need to expose any writer. This...

> […] the cgo based package by _youtube/vitess_ project was amazingly better. Hence, I got convinced into making sure you didn't get to put go's standard gzip package in here....

> The documentation part is being a killer… Always! :) > Is your framework that is geared towards full websites open sourced? I'm only at the beginning (I develop full-time...