Support both Alice and Negroni

[doug]

Support both Alice and Negroni

[kisielk]

I'm not really sure what you're asking. Is it to change the way the handlers are constructed? or?

[doug]

Yes, I'm referring to the construction. I'm saying if the struct supported func ServeHTTP(rw http.ResponseWriter, r *http.Request, next http.HandlerFunc) you could also expose func(http.Handler)http.Handler using something like the Compose function I wrote above. Then both are available.

[doug]

I'm happy to create a pull request illustrating the idea if you think it prudent.

[kisielk]

I'd prefer if everything in the package stuck to the standard http.Handler API. There's a lot of people going in different directions with approaches to implementing middleware with none of them being the clear winner yet. At least net/http is a common denominator.

[doug]

Totally reasonable. I actually think the http.Handler -> http.Handler is the nicest api unless something different gets added to net/http. I would like the community to standardize, but I'm sure it will with time. Do you have a list somewhere of handlers people should be writing?

[kisielk]

Not really. I've just included ones I've used in my web applications and found to be generally useful, and a few others which users of the package have submitted.

[doug]

Cool, might be nice to have a roadmap on the wiki or readme of handlers for people to consider writing. For example, I have some caching handlers I use (browser cache, lru cache, memcache) I wrote which I could convert to this format if that is of interest.

[kisielk]

I don't really have a particular roadmap or vision beyond "a useful collection of http.Handler types" so if you think you have something useful just propose it :)