Correct me if I am wrong, but with MX and the Application scope, it is just writes that need to be locked (for simple reads to an array anyway). It isn't as if you are trying to get an instance of a singleton and changing values inside it while another thread is in the middle of using it.
So if this assumption is correct, you will only need to add on cflock tag around the initial creation, along with a check to see if it is already there, as per Barry's post. Your reads would stay the same. Shane On 11/18/06, Charlie Arehart <[EMAIL PROTECTED]> wrote: > > > Matthew said: > > > I've just read this article > > > ( > http://www.adobe.com/devnet/server_archive/articles/cf_locking_best_practic > es.html) > > on locking read/write to application scoop, however the article seems > old, > is this still relevant? Note: the project I'm working on does not use > application.cfc. > > Yes, that is indeed old news if you're on CFMX (6 or above). Here's a more > updated version of the state of affairs regarding locking and shared scope > variables: > > http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_18235 > > It's a shame that the older article doesn't point to the newer one. I'll > pass that on to someone in the company who may be able to help. > > /charlie > http://www.carehart.org/blog/ > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
