Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use "net/context" #73

Open
hut8 opened this issue Feb 23, 2016 · 1 comment
Open

Use "net/context" #73

hut8 opened this issue Feb 23, 2016 · 1 comment

Comments

@hut8
Copy link
Member

hut8 commented Feb 23, 2016

Currently we don't use net/context, but we should.
https://godoc.org/golang.org/x/net/context
Each piece of middleware, including the final handler, has no good context state. This is primarily irritating in the error handler, where we can't figure out what problems are because the value returned from panic() has no context other than the stack trace (i.e., no local variables, no URL, etc).

@joshjordan
Copy link
Member

This is neat.

On Tue, Feb 23, 2016 at 5:11 PM Liam [email protected] wrote:

Currently we don't use net/context, but we should.
https://godoc.org/golang.org/x/net/context
Each piece of middleware, including the final handler, has no good context
state. This is primarily irritating in the error handler, where we can't
figure out what problems are because the value returned from panic() has
no context other than the stack trace (i.e., no local variables, no URL,
etc).


Reply to this email directly or view it on GitHub
#73.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants