-
Notifications
You must be signed in to change notification settings - Fork 91
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 Singleton RaygunClient in RaygunHttpModule (.NET Framework) #537
Use Singleton RaygunClient in RaygunHttpModule (.NET Framework) #537
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good, just a couple of thoughts to discuss
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the change. Looks good, just comment on one optional minor thing that I didn't think of before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 👍
…onId cookie is present when request message is built.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Description
Update the
RaygunHttpModule
for ASP.NET Framework applications to store and use a singleRaygunClient
instance. This avoids a newRaygunClient
and in turn aThrottledBackgroundMessageProcessor
, from being created for every exception handled by theRaygunHttpModule
. TheThrottledBackgroundMessageProcessor
creates a number of background worker threads, so instantiating it for each exception can be costly.