Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
Date: Thu, 3 Apr 2014 04:23:15 +0000 (UTC)
From: "Jordan Zimmerman (JIRA)" <jira@apache.org>
To: dev@curator.apache.org
Message-ID: <JIRA.12680398.1384989739938.55824.1396498995928@arcas>
In-Reply-To: <JIRA.12680398.1384989739938@arcas>
References: <JIRA.12680398.1384989739938@arcas>
Subject: [jira] [Resolved] (CURATOR-74) Documentation on InterProcessMutex
 is misleading
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CURATOR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jordan Zimmerman resolved CURATOR-74.
-------------------------------------

    Resolution: Fixed

> Documentation on InterProcessMutex is misleading
> ------------------------------------------------
>
>                 Key: CURATOR-74
>                 URL: https://issues.apache.org/jira/browse/CURATOR-74
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.3.0
>            Reporter: Swarnim Kulkarni
>            Assignee: Jordan Zimmerman
>             Fix For: 2.4.2
>
>         Attachments: CURATOR-74.1.patch
>
>
> Documentation on the two acquire methods is slightly misleading as it does not make clear what the behavior should be if a thread owns a lock and another thread attempts to get the lock. The doc should be fixed.


--
This message was sent by Atlassian JIRA
(v6.2#6252)