You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have developed the resuming of chunked uploads in android.
Currently I store the upload id and the successful chunks. With these infos I can skip the successful parts and just upload the remaining ones.
To simplify the client code I thought of this:
use a reproducable id and not random id as now
allow to get the current successfull chunks as a list
With both enhancement the client does not need to store any information about the upload.
Reacted by Vinay Sastry, Dean Qin, Fabien Ménager, Konstantin Dmitriev, enoch85, Leonidas Villeneuve, Daniel Nauck, Git'Fellow, Timon Engelke, Tamás Nagy and 2 more
@icewind1991 told us that this would have the side-effect of preventing large files from being uploaded as they would have to be held in memory to be chunked. So we should find a way for the uploader to adapt its behaviour and not always use chunked mode.
Not from my (client team lead) side.
It is implemented on all clients, but not on web.
That is why it is in server repository.
So I cannot share any news on this…
I would like to try to work on this or at least clarify a little bit to help someone to finish it. @tobiasKaminsky could you point me how did you do in the android client?
I've seen old web client create and md5+time, the new one creates a random string.
Activity
PhenX commentedon Mar 8, 2017
This feature is a must-have for big files.
I integrated such a feature with this library which works like a charm : http://resumablejs.com/
jancborchardt commentedon May 16, 2017
This seems often requested – @karlitschek @LukasReschke @MorrisJobke @rullzer any plan here, maybe for 13?
ariselseng commentedon May 16, 2017
@jancborchardt For the web UI owncloud is doing a PR here: owncloud/core#26306
I think it is mostly finished.
karlitschek commentedon May 16, 2017
Yes. Improvement a lot of people want.
oparoz commentedon May 18, 2017
@icewind1991 told us that this would have the side-effect of preventing large files from being uploaded as they would have to be held in memory to be chunked. So we should find a way for the uploader to adapt its behaviour and not always use chunked mode.
rullzer commentedon May 18, 2017
@tobiasKaminsky if you are using the new chunking ng this is available. What is the webdav endpoint the android client uses?
tobiasKaminsky commentedon May 19, 2017
/remote.php/webdav
tcitworld commentedon Nov 10, 2017
Will this be into 13 ? I'll try to integrate ownCloud's work this week-end maybe.
7 remaining items
juliusknorr commentedon Aug 21, 2019
@tobiasKaminsky Repoening, as it is not yet implemented in the web ui
Cinerar commentedon Oct 15, 2019
Just a suggestion, take a look at https://tus.io/
https://github.com/ankitpokhrel/tus-php
tobiasKaminsky commentedon Oct 16, 2019
I fear that this is not possible to use as we need to rely on our dav protocol.
electrofloat commentedon Jan 28, 2023
Any news on this?
tobiasKaminsky commentedon Jan 30, 2023
Not from my (client team lead) side.
It is implemented on all clients, but not on web.
That is why it is in server repository.
So I cannot share any news on this…
manolopm commentedon Mar 10, 2024
I would like to try to work on this or at least clarify a little bit to help someone to finish it.
@tobiasKaminsky could you point me how did you do in the android client?
I've seen old web client create and md5+time, the new one creates a random string.
susnux commentedon Jul 31, 2024
How to do it: https://docs.nextcloud.com/server/stable/developer_manual/client_apis/WebDAV/chunking.html
WebUI is also using the new API and retry failed chunks only public shares are missing.