Hacker News Reader

The request context is I think the most annoying part of go http handling.

Oh you want to wrap your handler with something that does db.Begin()/db.Commit()? Well you need to stuff that tx somewhere...

so then your options are a global map[*http.Request]interface{} with mutexes or pass it as an arg. Passing it in as an arg means you either lose compile time type checking because you use reflect or lose the ability to add more middlewares that build up request context. The map[]interface{} also loses compile time type checking for the most part unless you do something per type of context, with more mutexes.

The second option is the sanest, but means either reflect if you have more than one context arg to build out (sql.Tx + cache + oauth grant + whatever else maybe?) or you have some common context object that may or may not use everything every request and your just adding more context members all the time that may or may not be initialized for that particular request.

Sometimes I miss the dynamic typing and/or compile time type templating.

View on HN

type handler struct { foo Foo } func (h *handler) bar(w http.ResponseWriter, req *http.Request) { // use h.foo } func (h *handler) qux(w http.ResponseWriter, req *http.Request) { // use h.foo } // later h := handler{ foo: someFoo, } http.HandleFunc("/bar", h.bar) http.HandleFunc("/qux", h.qux)