>> So user initiates a new upload already in progress under the same name, >> different file or not. Assuming on the server side you could check for >> uploads in progress already for that user/session,
That was the problem. What you get from the client on each form post was three fields the name of the file, the chuck data and the number of total chucks. If you open another browser window you have the same session ID so there was nothing unique about the two sessions and no way to track which page was sending the data. I thought of trying to keep track of what chunks had been sent but that because cumbersome and pointless of there were two different files with the same name. The solution was within Plupload itself. By programmatically adding another field to each individual file that was added to the queue containing a UUID or unique name I could use that to accept the files then not worry about multiple sessions or file names. Once the file was accepted then I would look for a name conflict and add a suffix (1), like Chrome does, to the file name. I have been running additional tests and it seems to work just fine with even very large (>1gig) files because each post is only 1 meg. Dennis Powers UXB Internet - A website Design and Hosting Company P.O. Box 6028, Wolcott, CT 06716 - T:203-879-2844 W: http://www.uxbinternet.com W: http://www.ctbusinesslist.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:358823 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
