Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 56AA110684 for ; Wed, 20 Nov 2013 23:24:01 +0000 (UTC) Received: (qmail 71167 invoked by uid 500); 20 Nov 2013 23:24:01 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 71120 invoked by uid 500); 20 Nov 2013 23:24:00 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 71092 invoked by uid 99); 20 Nov 2013 23:24:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Nov 2013 23:24:00 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 20 Nov 2013 23:23:58 +0000 Received: (qmail 69048 invoked by uid 99); 20 Nov 2013 23:23:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Nov 2013 23:23:36 +0000 Date: Wed, 20 Nov 2013 23:23:36 +0000 (UTC) From: "Swarnim Kulkarni (JIRA)" To: dev@curator.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CURATOR-74) Documentation on InterProcessMutex is misleading MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Swarnim Kulkarni created CURATOR-74: --------------------------------------- Summary: 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 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.1#6144)