Standardize on start/end, not offset/length for range requests

developmentseed / obstore

Simple, fast integration with Amazon S3, Google Cloud Storage, Azure Storage, and S3-compliant APIs like Cloudflare R2

https://developmentseed.org/obstore

MIT License

146 stars 3 forks source link

Standardize on start/end, not offset/length for range requests #71

Closed kylebarron closed 2 weeks ago

kylebarron commented 2 weeks ago

get_range, get_range_async, get_ranges, and get_ranges_async now use start/end instead of offset/length. This is for consistency with the range option of obstore.get.