You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking for a nice way of logging every request but it seems like the explicit calls to http.HandlerFunc (providing it Dispatch) make this a bit tough.
The text was updated successfully, but these errors were encountered:
Yes, agree. One of the design changes I have on mind is to introduce
request and response filters. Then logging can part of the response chain.
On Wednesday, May 8, 2013, Travis Cline wrote:
I was looking for a nice way of logging every request but it seems like
the explicit calls to http.HandlerFunc (providing it Dispatch) make this a
bit tough.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5
.
fyi, the filters branch has an implementation of Filters as mentioned earlier. You can add multiple chained filters on global, webservice and route level. Each filter can use information for the request or response. Using this , you can generic logging, authentication, metrices etc. I have added an example of filters as the first proof of implementation. Have to write some tests and docs before merging it into the master. Any comments are welcome.
I was looking for a nice way of logging every request but it seems like the explicit calls to http.HandlerFunc (providing it Dispatch) make this a bit tough.
The text was updated successfully, but these errors were encountered: