query TUS large uploads

Add a default mode for TUS via restapi that doesn't require a shared temp folder so we can have only one way of uploading

What does it mean by one way of uploading?

issue: PLIP: TUS reliable large uploads with simpler file upload UI in volto · Issue #5423 · plone/volto · GitHub

The restapi allows two ways to add file content.
This refers to having the UI use only tus and not having two modes that can be switched between depending on a setting at startup.

### TUS without temp folder
* use ZODB blobs to store partial uploads and then join them at the end
* Add a default mode for TUS via restapi that doesn't require a shared temp folder so we can have only one way of uploading

Query:

  1. Would changes be required in core Plone backend code to fully support using ZODB blobs for TUS? Or can this be contained just within RESTAPI?
  2. Are there any existing utilities in Plone/Zope that could help with concatenating or joining blobs that we should leverage?

yes this would require core plone changes since chunks will have to be stored inside the ZODB rather than a temp folder. For this reason this is not expected to be part of GSOC project and can be excluded. This means the knowledge needed is only frontend.

As we need to connect the frontend with the TUS RESTful APIs , we need to have some knowledge about Zope as well right? like the methods it uses and its functionality, even if we're not directly involved in core Plone changes related to ZODB storage.

@rahul2668 The restapi endpoint for TUS already exists and works. So you don't need to know python, zope or plone development. Just how to install and test against the backend. You only need to know Plone from an outside functionality point of view.