go-schwift/tests/largeobject_test.go, branch v2.0.0 Go client library for Swift (OpenStack object storage) aka Rackspace Cloud Files aka Memset Memstore update module path for v2 2024-07-08T13:58:53+00:00 Stefan Majewsky majewsky@gmx.net 2024-07-08T13:56:55+00:00 e1625d914fa3d9ac98a7db85ae5de13ee4d58fd6 






Remove context from struct, add ctx as first args to many functions
2024-07-01T14:12:52+00:00

Sandro Jäckel
sandro.jaeckel@gmail.com

2024-07-01T14:12:52+00:00

b7683ab8dcdeca10ff52d626a285edcf7c1db719












fix manually fixable lints
2024-07-01T11:18:09+00:00

Stefan Majewsky
majewsky@gmx.net

2024-07-01T11:18:09+00:00

5a783c56a98c225569abfa6fb12fdf55297fee9e












fix autofixable lints
2024-07-01T11:17:16+00:00

Stefan Majewsky
majewsky@gmx.net

2024-07-01T11:15:00+00:00

3c489c0e29486ce1a5900c4ff87f403ebbbb70fa












Fix linting errors
2022-10-28T10:55:16+00:00

Sandro Jäckel
sandro.jaeckel@sap.com

2022-10-26T13:23:04+00:00

8b38a040830109f19550e7329b82ec5caf76b321












Format with go 1.19
2022-10-26T12:05:42+00:00

Sandro Jäckel
sandro.jaeckel@sap.com

2022-10-26T09:31:22+00:00

04ce17415f25dbf10eba954212c8428ae630df88












add test for segment expiration
2018-09-06T12:53:01+00:00

Muhammad Talal Anwar
talalanwar@outlook.com

2018-09-06T12:53:01+00:00

127cfdcd847fef24f606b5c548fe90dc2b46549e












add test for large object expiration
2018-09-06T12:05:25+00:00

Muhammad Talal Anwar
talalanwar@outlook.com

2018-09-06T12:05:25+00:00

bc05e125f4850bedbe19c5ab29d4767139c846df












test coverage for large object operations
2018-05-02T20:20:28+00:00

Stefan Majewsky
majewsky@gmx.net

2018-05-02T20:20:28+00:00

f57a07087a53a14e9dbf6e1e01da88e4c0dc34a5












revamp the LargeObject API
2018-05-02T17:33:46+00:00

Stefan Majewsky
majewsky@gmx.net

2018-04-30T12:14:56+00:00

f9749638e3393f471d7e28362795689bf37cc023

I thought about this some more, and I believe the Writer-based approach
in the previous version of the LargeObject API does not scale: It makes
it very hard to write code that uploads segments without resorting to a
buffer the same size as the segments. I don't want gigabyte-scale
buffers filling up my RAM, so this commit switches to a different API
based on Readers. LargeObject.Append() now behaves very similar to
Object.Upload(), which I find quite nice.





I thought about this some more, and I believe the Writer-based approach
in the previous version of the LargeObject API does not scale: It makes
it very hard to write code that uploads segments without resorting to a
buffer the same size as the segments. I don't want gigabyte-scale
buffers filling up my RAM, so this commit switches to a different API
based on Readers. LargeObject.Append() now behaves very similar to
Object.Upload(), which I find quite nice.