go-schwift - Go client library for Swift (OpenStack object storage) aka Rackspace Cloud Files aka Memset Memstore

	Commit message (Collapse)	Author	Age	Files	Lines
*	fix manually fixable lints	Stefan Majewsky	2024-07-01	1	-1/+1
\|
*	fix autofixable lints	Stefan Majewsky	2024-07-01	1	-29/+29
\|
*	Fix linting errors	Sandro Jäckel	2022-10-28	1	-4/+2
\|
*	Format with go 1.19	Sandro Jäckel	2022-10-26	1	-2/+0
\|
*	add test for segment expiration	Muhammad Talal Anwar	2018-09-06	1	-4/+6
\|
*	add test for large object expiration	Muhammad Talal Anwar	2018-09-06	1	-19/+54
\|
*	test coverage for large object operations	Stefan Majewsky	2018-05-02	1	-0/+195
\|
*	revamp the LargeObject API	Stefan Majewsky	2018-05-02	1	-105/+69
\| \| \| \| \| \| \| \| \| \|	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.
*	add DeleteOptions to Object.Delete()	Stefan Majewsky	2018-04-30	1	-0/+71
\|
*	initial support for large objects	Stefan Majewsky	2018-04-30	1	-0/+362
	This has gone through a lot of iterations on my branch, and I'm quite happy with the parts of the API that exist now. Test coverage can still be better, and will get better in the following commits. The API is not yet finished: I want to add Options arguments to Object.Upload(), Object.Copy(), Object.Move() and Object.Delete() that specify how each of these operations affect existing segments (and, later, also existing symlinks). For Upload(), uploading in segments shall become as easy as flipping a single switch.