From f9749638e3393f471d7e28362795689bf37cc023 Mon Sep 17 00:00:00 2001 From: Stefan Majewsky Date: Mon, 30 Apr 2018 14:14:56 +0200 Subject: revamp the LargeObject API 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. --- tests/field_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tests/field_test.go') diff --git a/tests/field_test.go b/tests/field_test.go index 8166f2d..c8dcf7f 100644 --- a/tests/field_test.go +++ b/tests/field_test.go @@ -88,7 +88,7 @@ func TestFieldTimestamp(t *testing.T) { func TestFieldHTTPTimestamp(t *testing.T) { testWithContainer(t, func(c *schwift.Container) { obj := c.Object("test") - err := obj.Upload(nil, nil) + err := obj.Upload(nil, nil, nil) if !expectSuccess(t, err) { return } -- cgit v1.2.3