clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (CLEREZZA-834) Align LockableMGraphWrapper and DataSetLockedMGraph
Date Fri, 25 Oct 2013 13:14:31 GMT

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

Reto Bachmann-Gmür resolved CLEREZZA-834.
-----------------------------------------

    Resolution: Fixed

> 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)

Mime
View raw message