I build in a reset mechanism into my codebase, so that if i update an object in the file system, i just reset my singletons with a url parameter.
I don't think there's any issue at all with protecting the CFC ... any more than you would need to protect a template from being requested if you were overwriting it in the file system. Any thread would just wait until it was available ... or time out. Reinstatiating a function library takes only a few milliseconds. >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Behalf Of John Farrar >Sent: Monday, October 31, 2005 3:48 AM >To: [email protected] >Subject: RE: [CFCDev] Global Function Libraries > > >My question is what do you do to make sure you have a current >version of the >library running. Do you persist this or do you re-instantiate the CFC with >every call? Keeping this type of thing current is a big deal to me. And if >you find something that needs to be updated a persistant CFC would be >another issue with protecting the CFC from other requests while you were >updating the in memory version. (Right) > > > > >---------------------------------------------------------- >You are subscribed to cfcdev. To unsubscribe, send an email to >[email protected] with the words 'unsubscribe cfcdev' as the >subject of the email. > >CFCDev is run by CFCZone (www.cfczone.org) and supported by >CFXHosting (www.cfxhosting.com). > >An archive of the CFCDev list is available at >www.mail-archive.com/[email protected] > > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
