It poses an interesting question.  From what I know TC sends any changes made 
at the time any lock (nested or not) is exited.  So that would mean that the 
writes made under the outer write lock would get pushed when the inner read 
lock is released - so I don't know - this seems to be an odd case I am not sure 
I understand how the visibility vis a vis the Memory Model should behave. 


Someone want to clarify the exact intention of the code - and the behavior that 
we will or should exhibit? 

----- Original Message ----- 
From: "Steven Harris" <[EMAIL PROTECTED]> 
To: [email protected] 
Sent: Thursday, June 5, 2008 6:21:25 AM GMT -08:00 US/Canada Pacific 
Subject: Re: [tc-dev] Lock Downgrade... 

Doh, I didn't read carefully enough. Geert is 100 percent correct. 
Even more proof that it is a bug :-). I'll ask the dude to throw it in   
JIRA. 

On Jun 5, 2008, at 6:18 AM, Geert Bevin wrote: 

> 
> On 05 Jun 2008, at 15:00, Steven Harris wrote: 
> 
>> http://forums.terracotta.org/forums/posts/list/1124.page 
>> 
>> Interesting. I assume this is just an obscure bug. We don't 
>> intentionally have issues with downgrades like we do  upgrades 
>> right? 
> 
> Strictly speaking this is not even a downgrade since it's done on two 
> different locks, right? 
> 
> Definitely sounds like a bug, needs further investigation. I vaguely 
> remember something about the current active lock being stored on a   
> per- 
> thread basis somewhere. Might be that RRWL doesn't properly integrate 
> with that. 
> 
> -- 
> Geert Bevin 
> Terracotta - http://www.terracotta.org 
> Uwyn "Use what you need" - http://uwyn.com 
> RIFE Java application framework - http://rifers.org 
> Music and words - http://gbevin.com 
> 
> _______________________________________________ 
> tc-dev mailing list 
> [email protected] 
> http://lists.terracotta.org/mailman/listinfo/tc-dev 

_______________________________________________ 
tc-dev mailing list 
[email protected] 
http://lists.terracotta.org/mailman/listinfo/tc-dev 
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev

Reply via email to