Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com
 designates 74.125.82.179 as permitted sender)
Message-ID: <52F8F1B1.1020805@gmail.com>
Date: Mon, 10 Feb 2014 16:35:13 +0100
From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?= <elecharny@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [Mavibot] Transaction discussion
References: <52F4B178.3080606@symas.com>
	<CABzFU-fgooAAKtKywZ+WzkvvB=pd7ABtsqz3mtSCUzbiBhwh9A@mail.gmail.com>
	<52F51F03.1070002@gmail.com>
 <CABzFU-foW=o9CBpRQy2JJAqP8tzjV4QGDjJXMGwHLggDfr31vA@mail.gmail.com>
 <52F5F84D.3080706@gmail.com>
In-Reply-To: <52F5F84D.3080706@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

I think the ReadWriiteReentrantLock data structure is the right one to
deal with this situation :
http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/locks/ReentrantReadWriteLock.html

(Thanks to Cedric Champeau for the suggestion)


Le 2/8/14 10:26 AM, Emmanuel Lécharny a écrit :
> Le 2/8/14 8:28 AM, Kiran Ayyagari a écrit :
>> On Fri, Feb 7, 2014 at 11:29 PM, Emmanuel Lécharny <elecharny@gmail.com>wrote:
>>
>>>>> This is not trivial, as we want to make it as easy as possible for our
>>>>> users. Typically, how should an operation know which kind of transaction
>>>>> it is dealing with ? Let's have a look at such an operation :
>>>>>
>>>>> insert :
>>>>>     // check if we are already into a txn
>>>>>     if (in transaction)        (1)
>>>>>         then
>>>>>             process operation
>>>>>         else
>>>>>             start transaction  (2)
>>>>>             process operation
>>>>>             commit operation
>>>>>
>>>>> so far, it seems ok, but what if another thread has started a
>>>>> transaction *just* after the test (1) and before (2) ? This is
>>> complicated.
>>>>> hmmm, how about using ThreadLocal,
>>>> and not sure we need to branch based on the presence of txn handle, the
>>>> start transaction(2)
>>>> should always give the txn handle present in ThreadLocal
>>> That would work if only we were in a single thread environment... In our
>>> case, we have no idea how many threads will try to write data in Mavibot.
>>>
>>> ThreadLocal is meant for multithreaded environments
> Sure, but in this case, it won't help, as a ThreadLocal storage will be
> associated with one single thread (and each thread will have a different
> insance), when we are trying to avoid many threads to access one
> resource concurrently.  I'm failing to see how we could use TLS in this
> case. Do you have something in mind ?
>
>


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com