-
Notifications
You must be signed in to change notification settings - Fork 11
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
Server-configured timeouts per-archive #114
Labels
Comments
Apart from being too many configs, this may not even be very useful in the context of an aggregated response. Because the archive with the longest timeout is going to be the deciding one, so better just set the global timeout matching the longest one is willing to tolerate to any archive. Do you have any specific use cases in mind where this can be useful? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would like to specify different timeout rates on a per-archive basis. The current implementation seems to apply a universal set (Connection, Header, and Response) of timeout values onto each archive.
It would be useful to be able to specify this in the config file and have MemGator adjust its querying.
The text was updated successfully, but these errors were encountered: