-
Notifications
You must be signed in to change notification settings - Fork 4
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
AllocatorAwareContainer #37
Comments
I did look into making The challenge is that That said, I am open to alternative solutions, including replacing |
I'll use allocators in the future for a project as a form of resource control to mitigate DoS. This is a feature I'm interested in. What I do care about is heap usage. If |
How do you mitigate DoS? Do you use an allocator with bounded memory for incoming requests, and then ignore the request, and possibly close the connection, when an |
Each connection will have its own stateful allocator object. If the resource usage exceeds the limit for that connection ( Global objects that communicate with the internal pipeline are unbounded and will use the default implicit allocator. |
From #35
The text was updated successfully, but these errors were encountered: