Date: Tue, 8 May 2012 09:50:50 -0700 (PDT)
From: Po <fermar...@gmail.com>
To: mach-ii-for-coldfusion@googlegroups.com
Message-ID: <410070.2949.1336495850021.JavaMail.geo-discussion-forums@ynbv35>
In-Reply-To: <22540577.3147.1336495701841.JavaMail.geo-discussion-forums@ynmk20>
References: <22540577.3147.1336495701841.JavaMail.geo-discussion-forums@ynmk20>
Subject: Re: Locking mach-ii properties (thread-safety)
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_2947_823398.1336495850020"

------=_Part_2947_823398.1336495850020
Content-Type: multipart/alternative; 
	boundary="----=_Part_2948_14428410.1336495850020"

------=_Part_2948_14428410.1336495850020
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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.
>

------=_Part_2948_14428410.1336495850020
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

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?<br><br>On Tuesday, 8 May 2012 12:48:21 UTC-4, Po  wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">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).<br><br>Is there a reason for this, or is this never really an issue in your experience? (or maybe I am just completely misunderstanding something)<br><br>Thank you.<br></blockquote>
------=_Part_2948_14428410.1336495850020--

------=_Part_2947_823398.1336495850020--