storj/satellite/orders
Egon Elbre 10a0216af5 satellite/metainfo: use range for specifying download limit
Previously the object range was not used for calculating order limit.
This meant that even if you were downloading only a small range it would
account bandwidth based on the full segment.

This doesn't fully address the accounting since the lazy segment
downloads do not send their requested range nor requested limit.

Change-Id: Ic811e570c889be87bac4293547d6537a255078da
2021-06-01 09:36:55 +00:00
..
encryptionkey_test.go satellite/orders: add factory function to encryption key 2020-11-20 11:40:15 -08:00
encryptionkey.go satellite/orders: use smaller encrypted metadata 2021-01-08 16:40:31 +00:00
endpoint_test.go satellite/metabase: move package one level higher 2021-04-21 15:54:22 +03:00
endpoint.go all: fix error naming 2021-04-29 15:38:21 +03:00
orders_test.go satellite/orders: populate 2021-05-25 18:07:22 +00:00
rollups_chore.go satellite/orders: Flush all pending bandwidth rollup writes on shutdown 2020-01-23 08:12:41 -07:00
rollups_write_cache_test.go satellite/orders: add settled amount to rollups write cache 2020-07-07 14:46:06 +00:00
rollups_write_cache.go satellite/orders: Delete unused methods & DB tables 2021-02-01 18:01:29 +00:00
service_test.go satellite/metainfo: use range for specifying download limit 2021-06-01 09:36:55 +00:00
service.go satellite/metainfo: use range for specifying download limit 2021-06-01 09:36:55 +00:00
signer_test.go satellite/metabase: move package one level higher 2021-04-21 15:54:22 +03:00
signer.go satellite/metabase: move package one level higher 2021-04-21 15:54:22 +03:00
window_endpoint_phase.go satellite/orders: 3-phase rollout 2020-08-03 17:01:42 +00:00