29 Apr 2008 7:17 AM #231
So is a kind of "sequential" upload needed in your case?
29 Apr 2008 7:35 AM #232
Yes very much so. Even if one fails I still want the next one to upload, just have the icon turn to the error icon you already use.
29 Apr 2008 8:11 AM #233
This already works with both singleUpload:true and singleUpload:false.
29 Apr 2008 8:17 AM #234
Perhaps I am completely misunderstanding, but when I add multiple files to the UploadPanel via the add button, they all show up as a list, then when I click the Upload button each file's spinner starts and when I look at Firebug and my server, I see mutiple connections at the same time.
The way I have been testing this is with large files 10+ mb so I know it takes more then a couple seconds to upload.
I have tried the singleUpload: true, and singleUpload: false.
My understanding is that singleUpload: true is that only one file gets posted per form submit and singleUpload: false is all the files in the queue get submited in a single form submit.
Just to be clear, I am curious about having this:
1. FileOne.xml -> begins upload, when finished, whether failed or success, go to next.
2. FileTwo.xml -> then as each file gets upload each spinner starts, and shows success or error icon.
3. FileThree.xml ..
4. FileFour.xml ..
5. FileFive.xml -> until the last file gets uploaded.
29 Apr 2008 9:20 AM #235
singleUpload:true = one form with many file inputs posted and uploaded in one request.
singleUpload:false = many forms each with one file input uploaded in many requests.
29 Apr 2008 10:05 AM #236
singleUpload: false <-- perfect, however I want to make the requests dependent on the request ahead of it. So lets say an option of "simultaneousTransfers: 2", two will upload at the same time, when one finishes the next starts, or if it was set to 1, then only one will upload, once a finished status is returned, the next starts.
29 Apr 2008 10:14 AM #237
That is that concurrent:false that is not implemented. Still wondering why it's needed...
29 Apr 2008 10:25 AM #238
Well I am wanting this app to behave more like an FTP client you see in the world and to give the owner of the app the potential to restrict the amount of files uploaded at one time.
If you look at Filezilla for example you can queue files up and then set how many concurrent connections and then as one finishes the next starts.
I mean I can modify the code to do this I suppose, now that I have seen that concurrent is not implemented, before though I thought it was a bug that it wasn't working or a work in progress.
29 Apr 2008 5:51 PM #239
Any more thoughts Saki? Or how to go about implementing this?
29 Apr 2008 9:25 PM #240
I'll go into this anyway as I need to move filetree from beta phase to stable version. Now, I have some other things to do but I think that it will be feasible in 2-3 weeks...