Or is this something that was intended to be implemented as needed at the application level as opposed to being implemented at the framework level?
On Tuesday, 8 May 2012 12:48:21 UTC-4, Po wrote: > > As I was exploring some of Mach-II's code on Github, I noticed that if I > (hypothetically) happen to call the setProperty method from my app at some > point during the request to set a property to "A" if someTempFlag is true, > or to "B" if someTempFlag is false, I could then be causing race conditions > when there are multiple concurrent requests since there is no locking > implemented in the PropertyManager.cfc (nor in other component that calls > the setProperty method that I could find). > > Is there a reason for this, or is this never really an issue in your > experience? (or maybe I am just completely misunderstanding something) > > Thank you. > -- To post to this group, send email to [email protected] For more options and to unsubscribe, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en SVN: http://svn.mach-ii.com/machii/ Wiki / Documentation / Tickets: http://trac.mach-ii.com/machii/
