I have a Pylons application that provides web services for a Django-based interface. I need to be able to provide file upload and download to application users.
Basically, they upload a file in the interface (which can be literally anything and often quite large). The file is transferred from the client => django web server => pylons app server => internal file server.
The internal file server does not provide an API; the only way to place the file on it is scp. Thus, streaming is not relevant at the pylons => fserv stage. In addition, fserv cannot be accessed from the network layer at which the django application is running.
In the reverse process, fserv provides an HTTP access method for its files, which is not yet available for the web server, so I need to connect the stream from fserv => pylons => django.
What is the Pylons side of this process? How can I minimize the delay of these file operations? I know that I am stuck in a write operation, given that I have to send the whole file after receiving it.
Also, what does the Django side of this process look like? How to upload a file to the streaming download service and how to upload it?
To minimize the argument, suppose that I cannot change the main components of my system and that the firewalls and administrator policies do not allow the use of network shares to move files.
source
share