A few weeks ago we implemented a context that given some readClosers and writeClosers would track if any were idle and eventually cancel the context. We use this for handlers in our server. We seem to be having a crash though where we are effectively returning from a handler, and yet a read/write on a resp.Body might still be blocked I remember @bradfitz saying this was the only way to get out of the blocked read/write, should it be causing a panic (from inside the http pkg) if there is a read/write after the handler returns?
-- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
