On 6-Nov-08, at 7:48 AM, Koji Sekiguchi wrote:
> So that multiple threads can efficiently access the writer, but
only one thread at a time does a commit.
> Adding docs with the writer is the 'read' and committing is the
write. If I remember correctly.
You remember correctly, Mark. Because
> So that multiple threads can efficiently access the writer, but only
one thread at a time does a commit.
> Adding docs with the writer is the 'read' and committing is the
write. If I remember correctly.
You remember correctly, Mark. Because of the lock, is blocked
during , even if Concurrent
So that multiple threads can efficiently access the writer, but only
one thread at a time does a commit. Adding docs with the writer is the
'read' and committing is the write. If I remember correctly.
- Mark
On Nov 6, 2008, at 6:24 AM, Koji Sekiguchi <[EMAIL PROTECTED]> wrote:
I'm sorry i
I'm sorry if this is a stupid question but I'm curious
why DUH2 uses ReentrantReadWriteLock.
What is the purpose of it?
Thank you,
Koji
