synchronization

I am looking for methods, built-in functions, good practices... to append new data to a matrix - when the rows and columns are not the same The data I deal with is structured as follows: A.values: Ta x Ma matrix of values A.dates: Ta x 1 vector of datenum A.id: 1 x Ma cell array of ids Now the challenge is how to deal with new (potentially overlapping) data B that I load in and would like to append to a new matrix C : When new data comes in, it can expand both horizontally and vertically due to: new ids new dates It also can have dates that start before min(A.dates) or after max(A.dates) or

I have an object whose internal mutable state is being constantly updated by one or more threads. The object is synchronized, and the goal is to periodically save its state (via serialization) from yet another thread: public class Counter implements Serializable { private int dogCount; private int catCount; public synchronized void updateFromDogThread( int count ) { dogCount = count; } public synchronized void updateFromCatThread( int count ) { catCount = count; } } Questions: Is serialization safe in this case? How does it work under the hood? That is to say, will the ObjectOutputStream

Code snippet - 1 class RequestObject implements Runnable { private static Integer nRequests = 0; @Override public void run() { synchronized (nRequests) { nRequests++; } } } Code snippet - 2 public class Racer implements Runnable { public static Boolean won = false; @Override public void run() { synchronized (won) { if (!won) won = true; } } } I was having a race condition with the first code snippet. I understood that this was because I was obtaining a lock on an immutable object(of type Integer). I have written a second code snippet which is again impervious to 'Boolean' being immutable. But

I am trying to understand the difference between the two following code blocks AtomicBoolean ab = new AtomicBoolean(false); using the following to get and set state. . ab.get(); ab.set(X); vs. private boolean ab = false; private final Object myboollock = new Ojbect(); public void setAB(boolean state) { synchronized(myboollock) { ab = state; } } public boolean getAB() { synchronized(myboollock) { return ab; } } I need to thread protect a boolean, that is all, and have in the past used the later method, but would like to start to use Atomic objects, (if ) they are safe?, There are a few subtle

I found chromium issue titled "Allow extensions/apps to sync their own settings" that has status ' Fixed '. It's from December 2011. So, does it work? If so, how does it work and where are the docs? Last time similar question was asked in 2010 and then the answer was to use bookmarks hack. I think it's time to have an update on this topic. Update : I just found these docs for experimental chrome.storage API. Is this what I'm looking for? Do we have any new alternatives (other than bookmarks) till chrome.storage goes stable? chrome.experimental.storage was introduced as an experimental API in

Motivation: I'm working on an app that makes several (client) phones read audio data from a (server) phone. The idea is that they must all play the song at the exact same time together. Premise: I must figure out a way to make all phones start at a certain time stamp that is absolute (ie it's not relative to the use set clock of either phone etc..).. based on some research I figured the best way to do this is to use CFAbsoluteTimeGetCurrent(); The idea here is that I get the latency it takes the server to communicate with each phone (b/c GKSession is done serially not in parallel apparently),