Mailing-List: contact user-help@curator.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@curator.incubator.apache.org
MIME-Version: 1.0
Reply-To: vines@apache.org
In-Reply-To: <F8D4C201-8976-42ED-9431-7105F2AF4525@jordanzimmerman.com>
References: 
 <CADczPYR81yZrKD6DKYXAAZjinjBnOSNLDgEe8kpA3ksCtzWKOw@mail.gmail.com>
 <F8D4C201-8976-42ED-9431-7105F2AF4525@jordanzimmerman.com>
From: John Vines <vines@apache.org>
Date: Tue, 10 Sep 2013 23:31:16 -0400
Message-ID: 
 <CADczPYT+wRTGLK9cOS23eGEjm4DFSXJ+CPwVTeqFa12JC4oYBw@mail.gmail.com>
Subject: Re: InterProcessReadWriteLock
To: user@curator.incubator.apache.org
Content-Type: multipart/alternative; boundary=089e0158cb926e319b04e6134349

--089e0158cb926e319b04e6134349
Content-Type: text/plain; charset=ISO-8859-1

Awesome, thanks!


On Tue, Sep 10, 2013 at 6:19 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:

> > what happens if I attempt to acquire a write lock while there are read
> lock's in position?
> The writer waits until all readers release.
>
> > If the former, will it still block for the reader who's attempting to
> claim the writer?
> Just like JDK locks, upgrading from a read lock to the write lock is not
> possible. That would be a deadlock as the writer will wait indefinitely for
> the read to release.
>
> -JZ
>
> On Sep 10, 2013, at 5:10 PM, John Vines <vines@apache.org> wrote:
>
> > Quick question about the behavior of the InterProcessReadWriteLock's
> locking behavior- what happens if I attempt to acquire a write lock while
> there are read lock's in position? Will it block until the reader's are
> released or will it attempt to revoke the reader's locks? If the former,
> will it still block for the reader who's attempting to claim the writer?
> >
> > Thanks
> > John
>
>

--089e0158cb926e319b04e6134349
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Awesome, thanks!</div><div class=3D"gmail_extra"><br><br><=
div class=3D"gmail_quote">On Tue, Sep 10, 2013 at 6:19 PM, Jordan Zimmerman=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:jordan@jordanzimmerman.com" target=
=3D"_blank">jordan@jordanzimmerman.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">&gt; what happens if I att=
empt to acquire a write lock while there are read lock&#39;s in position?<b=
r>


</div>The writer waits until all readers release.<br>
<div class=3D"im"><br>
&gt; If the former, will it still block for the reader who&#39;s attempting=
 to claim the writer?<br>
</div>Just like JDK locks, upgrading from a read lock to the write lock is =
not possible. That would be a deadlock as the writer will wait indefinitely=
 for the read to release.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-JZ<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
On Sep 10, 2013, at 5:10 PM, John Vines &lt;<a href=3D"mailto:vines@apache.=
org">vines@apache.org</a>&gt; wrote:<br>
<br>
&gt; Quick question about the behavior of the InterProcessReadWriteLock&#39=
;s locking behavior- what happens if I attempt to acquire a write lock whil=
e there are read lock&#39;s in position? Will it block until the reader&#39=
;s are released or will it attempt to revoke the reader&#39;s locks? If the=
 former, will it still block for the reader who&#39;s attempting to claim t=
he writer?<br>


&gt;<br>
&gt; Thanks<br>
&gt; John<br>
<br>
</div></div></blockquote></div><br></div>

--089e0158cb926e319b04e6134349--