Niko Föhr

*This clearly needs some more thinking with better good night's sleep. Here are some fast notes. These are not necessarily answering to anything, but they can help us later when...

I was thinking that I would have had more time today to think this through, but unfortunately that did not happen. I wish I had few hours just to think...

Hi @cainmagi , If I understood this correctly, this > As I have proposed before, the locally fired callback function needs to send a request to the remote service, and...

What I am basically saying is that one needs to have one call to `du.configure_upload` (to open a route in the Flask app and define output folder) for each `du.Upload`...

Thanks for the explanations! A diagram would surely help to understand the working principle much faster! If we would use `du.configure_upload` for Flask apps the `upload_api` parameter documentation does not...

I think there are some kind of locks already in use, if I remember correctly. What I was thinking is that if there are two du.Upload components, and both of...

Related incoming changes in this PR: https://github.com/np-8/dash-uploader/pull/36

Oh yeah the locking is implemented by a file. I don't know why (it was there when I forked this), and as it works I have not needed to touch...

Yeah this definitely needs very detailed automated testing as adding two upload components makes things a lot more complicated. I think this will proceed very nicely after there is some...

Interesting. There were previously problems if `requests_pathname_prefix` and/or `routes_pathname_prefix ` were used, as discussed in https://github.com/np-8/dash-uploader/issues/3, and it these were fixed in v.0.3.0. Then, there were issues if `url_base_pathname` was...