You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@clerezza.apache.org by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org> on 2013/10/25 08:25:36 UTC

[jira] [Created] (CLEREZZA-834) Align LockableMGraphWrapper and DataSetLockedMGraph

Reto Bachmann-Gmür 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ür
            Assignee: Reto Bachmann-Gmür


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



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