Michael Eischer 8e1e3844aa backend: factor out connection limiting and parameter validation ... The SemaphoreBackend now uniformly enforces the limit of concurrent backend operations. In addition, it unifies the parameter validation. The List() methods no longer uses a semaphore. Restic already never runs multiple list operations in parallel. By managing the semaphore in a wrapper backend, the sections that hold a semaphore token grow slightly. However, the main bottleneck is IO, so this shouldn't make much of a difference. The key insight that enables the SemaphoreBackend is that all of the complex semaphore handling in `openReader()` still happens within the original call to `Load()`. Thus, getting and releasing the semaphore tokens can be refactored to happen directly in `Load()`. This eliminates the need for wrapping the reader in `openReader()` to release the token.		2023-04-14 22:32:15 +02:00
..
config_test.go	backend, options: Prefer strings.Cut to SplitN	2022-12-02 19:19:14 +01:00
config.go	backend: Don't Wrap errors from url.Parse	2022-12-17 09:41:07 +01:00
s3_test.go	test: Use testing.T.Cleanup to remove tempdirs	2022-12-09 14:23:55 +01:00
s3.go	backend: factor out connection limiting and parameter validation	2023-04-14 22:32:15 +02:00