eea1f58dbc
Right now, we spawn potentially several connections without necessarily needing to. For example, if we're transferring two objects, we can practically use at most three connections: one for the batch and one for each object. Instead of spawning all the workers up front, let's change how we do things and simply pass in the worker number at first. Then, acquire the connection when we're uploading or downloading so that the connection is only spawned on demand. This means that we spawn fewer workers in case there are few objects. |
||
---|---|---|
.. | ||
schemas | ||
adapterbase.go | ||
api_test.go | ||
api.go | ||
basic_download.go | ||
basic_upload.go | ||
custom_test.go | ||
custom.go | ||
errors_test.go | ||
errors.go | ||
manifest_test.go | ||
manifest.go | ||
meter.go | ||
ssh.go | ||
transfer_queue_test.go | ||
transfer_queue.go | ||
transfer_test.go | ||
transfer.go | ||
tus_upload.go | ||
verify_test.go | ||
verify.go |