server side file downloads

[Jereson2000]

Explanation:

Lets suppose we have 3 things API, backend-service (server) and frontend-service (client/worker) .

When creating a task a.k.a sending an .py file to the backend via the API the API downloads a copy for itself of the file
and the file gets to the worker in incomprehensible ways. Then if we close the server the files downloaded for the API will persist but the server will think that they have been deleted because the knowledge of these files is saved in memory. This raises and bug where if you try to create a new task with the same name you will receive an error that the task has already been created with that name but you will not see the task in the tasks list.

We discussed this issue and it was meant to implemented so that the files sent to the API are actually saved in the server side.
Here is some guidelines on how this should be implemented:

1. The backend-service needs a method that receives files and adds them to a uploads folder.
2. The api should have a method that receives files from users and sends them to the backend-service.
3. The GET .../tasks should be modified from the api so that the backend-service will tell if there are any tasks available.