From 55f08f9fb3a4927f654c54fcda6afa4992e51be1 Mon Sep 17 00:00:00 2001 From: Teyras Date: Tue, 10 Jan 2017 22:22:25 +0100 Subject: [PATCH] more about file uploads --- Rewritten-docs.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/Rewritten-docs.md b/Rewritten-docs.md index 14ee214..e46ec85 100644 --- a/Rewritten-docs.md +++ b/Rewritten-docs.md @@ -1489,12 +1489,17 @@ container implementation. #### Uploading files -There are two cases when users need to upload files using the API – submitting +There are two cases when users need to upload files using the API -– submitting solutions to an assignment and creating a new exercise. In both of these cases, -the final destination of the files is the fileserver. - -However, the fileserver is not publicly accessible, so the files have to be -uploaded through the API. +the final destination of the files is the fileserver. However, the fileserver is +not publicly accessible, so the files have to be uploaded through the API. + +The files can be either forwarded to the fileserver directly, without any +interference from the API server, or stored and forwarded later. We chose the +second approach, which is harder to implement, but more convenient -- it lets +exercise authors double-check what they upload to the fileserver and solutions +to assignments can be uploaded in a single request, which makes it easy for the +fileserver to create an archive of the solution files. @todo permission handling, roles, etc.