From: Robert Klemme <shortcutter@...>
Date: 2006-05-04T21:34:45+09:00
Subject: Re: concurrency question

2006/5/3, Eric Hodel <drbrain@segment7.net>:
> On May 3, 2006, at 12:58 PM, Trish Ball wrote:
>
> > I am new to concurrency issues, and am working with DRb (also new to
> > this).  My DRb class assigns a value to an instance variable that will
> > be accessed by my client.  Is there a possibility with a concurrency
> > issue if the client tries the access that variable when it is being
> > assigned.
>
> No.
>
> > @list = LabelList.new(@label_list)
> >
> > Will I need a mutex around this?
>
> It will see either the old value or the new value.  Nothing will
> break otherwise.

IMHO this cannot be answered correctly with the information we have so
far.  You are right with regard to assignment semantics (i.e.
assignment is atomic in current Ruby runtime) but inconsistencies
might still occur if the object is to be changed or if there are other
instance variables that have to be changed consistently.  It really
depends on the application context.

Kind regards

robert


--
Have a look: http://www.flickr.com/photos/fussel-foto/