Mailing-List: contact dev-help@clerezza.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@clerezza.apache.org
Date: Fri, 25 Oct 2013 06:25:36 +0000 (UTC)
From: =?utf-8?Q?Reto_Bachmann-Gm=C3=BCr_=28JIRA=29?= <jira@apache.org>
To: clerezza-dev@incubator.apache.org
Message-ID: <JIRA.12675751.1382682306199.752.1382682336142@arcas>
In-Reply-To: <JIRA.12675751.1382682306199@arcas>
References: <JIRA.12675751.1382682306199@arcas>
Subject: [jira] [Created] (CLEREZZA-834) Align LockableMGraphWrapper and
 DataSetLockedMGraph
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Reto Bachmann-Gm=C3=BCr created CLEREZZA-834:
-------------------------------------------

             Summary: Align LockableMGraphWrapper and DataSetLockedMGraph
                 Key: CLEREZZA-834
                 URL: https://issues.apache.org/jira/browse/CLEREZZA-834
             Project: Clerezza
          Issue Type: Improvement
            Reporter: Reto Bachmann-Gm=C3=BCr
            Assignee: Reto Bachmann-Gm=C3=BCr


One hand its about removing code duplication on the other hand there is a s=
light difference in the locking: LockableMGraphWrapper also locks when retu=
rning and iterator and the returned iterator locks on access. Clearly a cli=
ent should lock before getting and till finished using the iterator. So whi=
le the Locking in LockableMGraphWrapper  does not prevent the client from g=
etting ConcurrentModificationException it might (not sure) prevent another =
read from getting an exception while writing.


--
This message was sent by Atlassian JIRA
(v6.1#6144)