Server-configured timeouts per-archive

oduwsdl / MemGator

A Memento Aggregator CLI and Server in Go

https://memgator.cs.odu.edu/api.html

MIT License

56 stars 11 forks source link

Server-configured timeouts per-archive #114

Open machawk1 opened 5 years ago

machawk1 commented 5 years ago

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.

ibnesayeed commented 5 years ago

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?