I always like the easiest solution... When you send the file, append a UUID to the filename then strip it off when done. If he tries to send 2 files with the same name, when you strip off the UUID, check if that original filename is present already - if it is, make it unique (add a _2 or _3, etc... checking each time for conflict)
>I wonder if something server side could handle this maybe as well. > >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, return an error code to >the client? Overhead would be minimal as you would only really have to >perform the check on the first block of a file being uploaded. > > >Byron Mann >Lead Engineer & Architect >HostMySite.com >On Jul 4, 2014 12:07 PM, "UXB" <[email protected]> wrote: > > > > > Byron, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:358822 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
