incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Manuel Innerhofer <>
Subject filter() and interator() of LockableMGraphWrapper
Date Wed, 10 Nov 2010 10:57:16 GMT
Hi Reto,

I had a closer look at filter() and iterator() of LockableMGraphWrapper. I
seems to
me that the readlocks done in these methods and the LockableIterator are
unnecessary and performance impairing. The LockableIterator locks the graph
for every call of next() and hasNext(), but in between calls the graph is
not read-locked,
therefore a write operation can occur.
Because of this a caller of one of these methods has to read-lock the graph
iteratating anyway. I propose to no longer use LockableIterator in filter()
and iterator().
What do you think?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message