Properties are more intended to be static values for the most part and should never (I hate using "never", but I will stick with it in this case!) change per request or per user. Think of them in the same way that you would application variables in a procedural application. If you are looking to set temp values, I would recommend using eventArgs as they only span the life of the request.
@dshuck On Tue, May 8, 2012 at 11:48 AM, Po <[email protected]> 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/ > -- 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/
