Well, if you move the actual <cffile> operation to a separate CFC and instantiate that for every method call, you'll be fine (or <cfinvoke component="name" method="doUpload" ...>).
I think this is what has been saving me. The architecture I use creates new instances of stateless components on every request, with only a couple component instances being stored in session scopes (which are obviously far less susceptible to race conditions). I certainly agree that this is a little scary, though. I will make sure the CF team sees this thread.
Christian
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
