Currently, when one download is started from the web UI, the web UI stalls until the download is completed. The download process should probably be asynchronous so the web UI can continue to be used and new downloads started or configuration edited/viewed. Ideally this should have a thread pool/queueing mechanism underlying so users don't just end up spawning dozens of download processes at once.
Currently, when one download is started from the web UI, the web UI stalls until the download is completed. The download process should probably be asynchronous so the web UI can continue to be used and new downloads started or configuration edited/viewed. Ideally this should have a thread pool/queueing mechanism underlying so users don't just end up spawning dozens of download processes at once.