Re: [morph-developer] Synchronization in GetPropertyConverter

[Matt B. <gud...@ya...>]

I think it's necessary to leave get/setConverter
synchronized whenever your "if unset, set a default
converter" pattern is used.

-Matt B

--- Matt Sgarlata
<Mat...@wh...> wrote:

> How about the Converter reference?
> 
> I was thinking about this some more over lunch, and
> I think I read 
> somewhere else that pointers actually do need to be
> synchronized because 
> changing their values is not atomic on 64-bit
> systems.
> 
> Unfortunately, I have no clue where to look this
> stuff up.  I guess for 
> now unsynchronize propertyName (since it is
> immutable) and leave the 
> Converter synchronized?  For all the other Morph
> classes out there that 
> don't have synchronization on their getters/setters,
> I guess we can just 
> leave it alone until someone has a problem with it. 
> Usually 
> transformers are configured only once anyway, at
> least when I am using them.
> 
> Matt S
> 
> Matt Benson wrote:
> > I can agree here that the propertyName
> setter/getter
> > don't necessarily need to be synchronized.  I
> would be
> > so bold as to say, however, that synchronization
> > issues should be examined on a case-by-case basis.
>  :)
> >
> > -Matt B
> 
> 
>
-------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get
> the chance to share your
> opinions on IT & business topics through brief
> surveys-and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> morph-developer mailing list
> mor...@li...
>
https://lists.sourceforge.net/lists/listinfo/morph-developer
> 



       
____________________________________________________________________________________
The fish are biting. 
Get more visitors on your site using Yahoo! Search Marketing.
http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php