-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathblog.html
More file actions
252 lines (169 loc) · 9.65 KB
/
blog.html
File metadata and controls
252 lines (169 loc) · 9.65 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
<title>Blog</title>
<link rel="shortcut icon" href="/assets/img/favicon.ico">
<link href="/assets/bootstrap/css/bootstrap.css" rel="stylesheet" media="screen">
<link href="/assets/css/main.css" rel="stylesheet" type="text/css" />
<link href="//kvz.github.io/on-the-githubs/css/on-the-githubs.min.css" rel="stylesheet" />
<link href="http://feeds.feedburner.com/tusio" type="application/rss+xml" rel="alternate" title="Posts">
</head>
<body>
<a target="_blank" href="https://github.com/tus"><img style="position: absolute; top: 0; right: 0; border: 0; z-index: 10;" src="https://s3.amazonaws.com/github/ribbons/forkme_right_gray_6d6d6d.png" alt="Fork me on GitHub"></a>
<div class="container-narrow">
<div class="masthead">
<ul class="nav nav-pills pull-right">
<li class=""><a href="/index.html">Home</a></li>
<li class=""><a href="/about.html">About</a></li>
<li class="active"><a href="/blog.html">Blog</a></li>
<li class=""><a href="/demo.html">Demo</a></li>
<li class=""><a href="/protocols/resumable-upload.html">Protocol</a></li>
<li class=""><a href="/implementations.html">Implementations</a></li>
</ul>
<h3 class="muted logo"><a href="/">tus</a></h3>
</div>
<hr>
<!-- <h2>Blog</h2> -->
<h2><a href="/blog/2013/05/08/protocol-v0.2.1">Protocol v0.2.1</a></h2>
<p>
<span>Published: May 8, 2013</span>.
<span>Author: <a target="_blank" href="http://twitter.com/felixge">Felix Geisendörfer</a></span>
<br />
</p>
<p>This is a minor protocol release:</p>
<ul>
<li>Fix <a href="https://github.com/tus/tus-resumable-upload-protocol/pull/19">#19</a>:
Final-Length header was called Final-Size in one place by accident. (<a href="https://github.com/vayam">Naren
Venkataraman</a>)</li>
<li>Define that PATCH requests MUST use <code>application/offset+octet-stream</code> as the
<code>Content-Type</code>. (<a href="https://github.com/felixge">Felix Geisendörfer</a>)</li>
<li>Define that <code>Final-Length</code> values MUST NOT be negative. (<a href="https://github.com/felixge">Felix
Geisendörfer</a>)</li>
</ul>
<p>All patches can be seen <a href="https://github.com/tus/tus-resumable-upload-protocol/compare/v0.2...v0.2.1">here</a>.</p>
<h2><a href="/blog/2013/05/01/protocol-v0.2">Protocol v0.2</a></h2>
<p>
<span>Published: May 1, 2013</span>.
<span>Author: <a target="_blank" href="http://twitter.com/felixge">Felix Geisendörfer</a></span>
<br />
</p>
<p>After releasing our first draft a few weeks ago, we received an incredible
amount of feedback and suggestions. Based on this feedback as well as
<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2013AprJun/0155.html">discussing</a>
the problems with the <a href="http://trac.tools.ietf.org/wg/httpbis/trac/wiki">IETF HTTPbis Working
Group</a>, we identified a few
key issues with <a href="https://github.com/tus/tus-resumable-upload-protocol/blob/v0.1/README.md">v0.1</a> of the
protocol:</p>
<ul>
<li><code>PUT</code> requests are not appropiate for transfering partial resources</li>
<li>The <code>Content-Range</code> and <code>Range</code> headers are not meant for resuming an
interrupted resource transfer.</li>
</ul>
<p>After lots of careful thinking, we came up with a new approach that uses:</p>
<ul>
<li><code>PATCH</code> instead of <code>PUT</code></li>
<li>A new <code>Offset</code> header used by <code>HEAD</code> responses and <code>PATCH</code> requests alike</li>
<li>A <code>Final-Length</code> header to provide the final file size to the server</li>
</ul>
<p>We also split the protocol into a core protocol which takes care of
resumability, and nothing else, as well as optional protocol extensions.</p>
<p>The result of this has just been published as v0.2 can be seen on the <a href="/protocols/resumable-upload.html">protocol
page</a>. Also included is a new <a href="/protocols/resumable-upload.html#7">FAQ
section</a> which will expanded over time.</p>
<p>We feel that the overall result is a drastic simplification of the problem down
to its essence, and we encourage interested developers to implement prototypes.</p>
<p>Our next step is upgrading tusd, the jquery client and the ios client to the
new protocol version. Once the protocol has reached a little more maturity, we
are also thinking about providing an executable protocol verification tool for
implementers.</p>
<h2><a href="/blog/2013/04/15/a-protocol-for-resumable-file-uploads">A protocol for resumable file uploads</a></h2>
<p>
<span>Published: April 15, 2013</span>.
<span>Author: <a target="_blank" href="http://twitter.com/felixge">Felix Geisendörfer</a></span>
<br />
</p>
<p><strong>tl;dr:</strong> We are happy to announce version 0.1 of the <a href="/protocols/resumable-upload.html">tus resumable upload
protocol</a> and are interested in your
feedback!</p>
<p>With mobile devices becoming the dominant source of user generated media files,
reliable file uploading through unreliable mobile networks has become an
important issue for anybody interested in content acquisition.</p>
<p>Reliability here means the ability to detect network errors, and resuming an
upload without having to start from the beginning. In many scenarios this can
mean the difference between a file reaching your application, or the user
giving up in frustration.</p>
<p>Ideally, this should be a trivial feature to add. In reality however, there is
quite a lack of solutions in this space. Sure, there are a few JavaScript
libraries that claim to support resumable uploading, but in reality you will
end up spending a lot of time coming up with your own API for it, or
implementing a poorly specified one specific to a library. This is incredibly
frustrating, especially if you are planning to support this feature on multiple
platforms such as HTML5, iOS and Android.</p>
<p>Now, if you're a big company like Google, you may sit down and create such a
protocol for your needs. And in fact, Google has been working on a <a href="http://code.google.com/p/gears/wiki/ResumableHttpRequestsProposal">such a
protocol</a>
since 2010, for the now defunct Google Gears. The latest incarnation of this
are two incompatible protocols for <a href="https://developers.google.com/drive/manage-uploads">Google
Drive</a> and
<a href="https://developers.google.com/youtube/v3/guides/using_resumable_upload_protocol">YouTube</a>.
But unfortunately both of these protocols rely on a non-standard http status
code (<code>308 Resume Incomplete</code>), and are far from being generic enough for
general adoption.</p>
<p>This means that smaller companies are currently doomed to invent, implement and
maintain their own incompatible protocols and solutions for something that
should be a trivial component of a modern application.</p>
<p>We find this unacceptable, so the <a href="http://www.tus.io/">tus project</a> is a
community project that was born in order to level the playing field and make
resumable file uploading easy for anybody to implement.</p>
<p>Today we are happy to release version 0.1 of <a href="/protocols/resumable-upload.html">our
protocol</a>. Interested developers are
encouraged to experiment with it, and we are very interested in any feedback
you may have.</p>
<p>Later this week we will also release some initial clients for
<a href="https://github.com/tus/tus-jquery-client">jQuery</a> and
<a href="https://github.com/tus/tus-ios-client">iOS</a>, so make sure to follow this blog
and these repositories for future updates!</p>
<h2><a href="/blog/2013/04/06/hello-world">Hello world</a></h2>
<p>
<span>Published: April 6, 2013</span>.
<span>Author: <a target="_blank" href="http://twitter.com/kvz">Kevin van Zonneveld</a></span>
<br />
</p>
<p>Hey everybody, we're starting a new blog here to discuss file uploading, and
the protocol we are working on. So keep an eye on this space!</p>
<hr />
Subscribe to this blog via
<a href="http://feeds.feedburner.com/tusio">RSS</a>.
<!-- or
@todo(felixge) Hook in feedburner
<a href="http://tus.io/atom.xml?email=true">E-Mail</a>. -->
<hr>
</div>
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-3306079-17']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
<script src="/assets/bootstrap/js/bootstrap.js"></script>
<script src="//kvz.github.io/on-the-githubs/js/jquery.on-the-githubs.min.js"></script>
<script src="/assets/js/jquery-file-upload/js/vendor/jquery.ui.widget.js"></script>
<script src="/assets/js/jquery-file-upload/js/jquery.fileupload.js"></script>
<script src="/assets/js/jquery.tus.js"></script>
<script type="text/javascript">
window.tusdEndpoint = '';
</script>
<script type="text/javascript">
$('.on-the-githubs').onthegithubs();
// If you use bootstrap and want to enable tooltips:
$('a[rel]').tooltip();
</script>
<script src="/assets/js/upload-demo.js"></script>
</body>
</html>