/tus
/api/dms/tus
Description | The TUS-Endpoints are for large file uploads and processing. Within this endpoints DMS Objects can be created or updated. Also the content of existing DMS Objects can be updated. The DMS Service support version 1.0 of TUS which is documented on tus.io. Large files are in this context 100 MB until 20 GB. If there is the need to upload even larger files to enaio please contact the Product Management of enaio. The performance of processing large files depends highly on the network bandwith between enaio Server ↔︎ DMS Microservices ↔︎ enaio Gateway ↔︎ Clients. Even on the server side, excluding the clients, there should at least by 100MBit/s, better 1000MBit/s or even higher. Additional to the endpoints, specified by TUS itself, the DMS Service offer endpoints for finalization of an Upload and retrieving the processing status. The finalization process is a asynchronus process where a JSON ticket is created and with which the current progress can be observed by a client. We highly recommend to test big file uploads seriously that they are working in the given infrastructure before there is a data lost in production. |
|---|---|
Request | POST, PATCH, HEAD, OPTIONS, DELETE |
Response | See tus.io |
Minimum Version | 6.12.0 |
Request | /api/dms/tus |
Result | See tus.io |