<feed xmlns='http://www.w3.org/2005/Atom'>
<title>go-schwift/tests/shared_test.go, branch v1.2.0</title>
<subtitle>Go client library for Swift (OpenStack object storage) aka Rackspace Cloud Files aka Memset Memstore
</subtitle>
<link rel='alternate' type='text/html' href='http://git.xyrillian.de/go-schwift/'/>
<entry>
<title>Fix linting errors</title>
<updated>2022-10-28T10:55:16+00:00</updated>
<author>
<name>Sandro Jäckel</name>
<email>sandro.jaeckel@sap.com</email>
</author>
<published>2022-10-26T13:23:04+00:00</published>
<link rel='alternate' type='text/html' href='http://git.xyrillian.de/go-schwift/commit/?id=8b38a040830109f19550e7329b82ec5caf76b321'/>
<id>8b38a040830109f19550e7329b82ec5caf76b321</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Format with go 1.19</title>
<updated>2022-10-26T12:05:42+00:00</updated>
<author>
<name>Sandro Jäckel</name>
<email>sandro.jaeckel@sap.com</email>
</author>
<published>2022-10-26T09:31:22+00:00</published>
<link rel='alternate' type='text/html' href='http://git.xyrillian.de/go-schwift/commit/?id=04ce17415f25dbf10eba954212c8428ae630df88'/>
<id>04ce17415f25dbf10eba954212c8428ae630df88</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>make tests work with Keystone auth</title>
<updated>2018-05-04T09:32:10+00:00</updated>
<author>
<name>Stefan Majewsky</name>
<email>majewsky@gmx.net</email>
</author>
<published>2018-05-04T09:32:10+00:00</published>
<link rel='alternate' type='text/html' href='http://git.xyrillian.de/go-schwift/commit/?id=bc7e256d490a179c5636a5cbdfae12ec1e2b08dc'/>
<id>bc7e256d490a179c5636a5cbdfae12ec1e2b08dc</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>add configurable User-Agent to Schwift, Gopherschwift</title>
<updated>2018-05-03T13:14:47+00:00</updated>
<author>
<name>Stefan Majewsky</name>
<email>majewsky@gmx.net</email>
</author>
<published>2018-05-03T13:14:47+00:00</published>
<link rel='alternate' type='text/html' href='http://git.xyrillian.de/go-schwift/commit/?id=0e685c1a6632f2f421713f677dd1ae691dedaa68'/>
<id>0e685c1a6632f2f421713f677dd1ae691dedaa68</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>add DeleteOptions to Object.Delete()</title>
<updated>2018-04-30T11:47:38+00:00</updated>
<author>
<name>Stefan Majewsky</name>
<email>majewsky@gmx.net</email>
</author>
<published>2018-04-30T11:47:38+00:00</published>
<link rel='alternate' type='text/html' href='http://git.xyrillian.de/go-schwift/commit/?id=b698287d0655420713bf6edfbc8de53da7c5a236'/>
<id>b698287d0655420713bf6edfbc8de53da7c5a236</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>initial support for large objects</title>
<updated>2018-04-30T08:04:36+00:00</updated>
<author>
<name>Stefan Majewsky</name>
<email>majewsky@gmx.net</email>
</author>
<published>2018-04-29T19:19:14+00:00</published>
<link rel='alternate' type='text/html' href='http://git.xyrillian.de/go-schwift/commit/?id=0df55a731aa3330f82d22b010a7a2a4d66521972'/>
<id>0df55a731aa3330f82d22b010a7a2a4d66521972</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>revamp the Headers API</title>
<updated>2018-03-11T18:41:33+00:00</updated>
<author>
<name>Stefan Majewsky</name>
<email>majewsky@gmx.net</email>
</author>
<published>2018-03-11T18:38:27+00:00</published>
<link rel='alternate' type='text/html' href='http://git.xyrillian.de/go-schwift/commit/?id=d23b4052c0866698b14ac13ac98581d9f5440a9b'/>
<id>d23b4052c0866698b14ac13ac98581d9f5440a9b</id>
<content type='text'>
1. Move common methods of AccountHeaders, ContainerHeaders,
   ObjectHeaders into a base type Headers.

2. Fold Headers into RequestOptions to remove one of the two optional
   arguments on request methods. The new Headers.ToOpts() method
   offers a nice experience for users passing Headers to request
   methods.

   The Update() methods keep the explicit Headers argument since the
   Headers argument is not optional there.

   The only downside is that we lose a bit of type-safety because
   RequestOptions takes any Headers instance, so e.g. ContainerHeaders
   could be passed to Object.Upload(). I believe the benefits outweigh
   this problem.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
1. Move common methods of AccountHeaders, ContainerHeaders,
   ObjectHeaders into a base type Headers.

2. Fold Headers into RequestOptions to remove one of the two optional
   arguments on request methods. The new Headers.ToOpts() method
   offers a nice experience for users passing Headers to request
   methods.

   The Update() methods keep the explicit Headers argument since the
   Headers argument is not optional there.

   The only downside is that we lose a bit of type-safety because
   RequestOptions takes any Headers instance, so e.g. ContainerHeaders
   could be passed to Object.Upload(). I believe the benefits outweigh
   this problem.
</pre>
</div>
</content>
</entry>
<entry>
<title>reorganize code</title>
<updated>2018-02-19T20:33:49+00:00</updated>
<author>
<name>Stefan Majewsky</name>
<email>majewsky@gmx.net</email>
</author>
<published>2018-02-19T20:30:33+00:00</published>
<link rel='alternate' type='text/html' href='http://git.xyrillian.de/go-schwift/commit/?id=60d4779889baedc44972d4749daa073efca3b25c'/>
<id>60d4779889baedc44972d4749daa073efca3b25c</id>
<content type='text'>
* Gophercloud dependencies move into subpackage gopherschwift.
* Tests move into subpackage tests (to avoid import cycles).
+ Rename "Client" to "Backend".
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Gophercloud dependencies move into subpackage gopherschwift.
* Tests move into subpackage tests (to avoid import cycles).
+ Rename "Client" to "Backend".
</pre>
</div>
</content>
</entry>
</feed>
