>
> There are two ideas I've used in the past to deal with filename uniqueness
> issues.
>
> One is to name the file itself using an arbitrary name, but store
> the "real"
> name in the database, and use that real name when pushing the file to
> somewhere else. That works well using CFCONTENT, of course.
>
> The other is to store files uploaded by one person in a unique
> subdirectory
> within the larger directory.
I've decided upon creating 20 outgoing directories - the template that
uploads the file goes through a cftry/catch block up to 20 times, each
having a <cffile nameconflict="ERROR">. If the file exists in all 20
directories then a new randomly named directory is created. All
directories, besides the 20 default, get deleted in my scheduled task every
night. I would have used cfcontent, but for some reason I couldn't get it
to work when calling files from a remote machine (cffile, cfdirectory, and
cfftp all work great) - I swear, I have had the most trouble with that tag.
>
> Dave Watts, CTO, Fig Leaf Software
> http://www.figleaf.com/
> voice: (202) 797-5496
> fax: (202) 797-5444
> ------------------------------------------------------------------
> ------------
> Archives: http://www.mail-archive.com/[email protected]/
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
