incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tommaso Teofili <tommaso.teof...@gmail.com>
Subject Re: Setter of message
Date Tue, 17 May 2011 07:40:11 GMT
I agree, a BSPMessage should be kept immutable.
Tommaso

2011/5/17 Edward J. Yoon <edwardyoon@apache.org>

> > My understanding is that immutable object has some advantages such as
> thread safety in the concurrent computation environment. So basically I
> prefer immutable object to mutable one.
>
> I agree w/ you.
>
> I just wanted to know whether there's some particular case, requires setter
> to avoid creating objects.
>
> Sent from my iPhone
>
> On 2011. 5. 17., at 오후 2:46, "ChiaHung Lin" <chl501@nuk.edu.tw> wrote:
>
> > Is there any reason that we have to allow the state change of BSPMessage?
> >
> > My understanding is that immutable object has some advantages such as
> thread safety in the concurrent computation environment. So basically I
> prefer immutable object to mutable one.
> >
> > But maybe some scenario that prevent us from constructing immutable
> BSPMessage?
> >
> > -----Original message-----
> > From:Edward J. Yoon <edwardyoon@apache.org>
> > To:hama-dev <hama-dev@incubator.apache.org>
> > Date:Tue, 17 May 2011 14:08:05 +0900
> > Subject:Setter of message
> >
> > Hi
> >
> > Should we add setter to BSPMessage?
> >
> > Sent from my iPhone
> >
> >
> > --
> > ChiaHung Lin
> > Department of Information Management
> > National University of Kaohsiung
> > Taiwan
>

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