On 11-09-14 04:20 PM, Marmaduke Woodman wrote: > > Hi > > I just joined this list, and being new to factor, I don't want to > comment on factor specific details, but I want to point out that a > general problem in this situation is coordinating reads and writes of > a common data structure. > > Typically you'd want the data structure to have a consistent state > when any read or write occurs, so you would need a way to coordinate > both the c and factor calls, assuming the calls could be run in > parallel. If that's what you'd want then take a look a rich hickey's > ideas on state and identity (clojure related stuff) for good thoughts > on this. > > If the calls all not parallel, then you wouldn't have a problem, I > think, but from the way you've described what you want to do, it > wasn't clear. > > Hope this helps. To those who factor better, does the language have > built in mechanisms for coordinating shared state like clojure ? > > Cheers > Marmaduke > > Hi Marmaduke
I think your point is very valid and I am worried about it. The struct would be written to by factor only and read by the daemon only but I don't know what will happen if the daemon reads half way through a factor write. I would like to learn more about shared state. Thanks ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA Learn about the latest advances in developing for the BlackBerry® mobile platform with sessions, labs & more. See new tools and technologies. Register for BlackBerry® DevCon today! http://p.sf.net/sfu/rim-devcon-copy1 _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
