synchronization

What is the point of the synchronization here? Why not just use mConnectedThread.write(out) ? The code snippet is from the BluetoothChat sample for Android (found here) /** * Write to the ConnectedThread in an unsynchronized manner * @param out The bytes to write * @see ConnectedThread#write(byte[]) */ public void write(byte[] out) { // Create temporary object ConnectedThread r; // Synchronize a copy of the ConnectedThread synchronized (this) { if (mState != STATE_CONNECTED) return; r = mConnectedThread; } // Perform the write unsynchronized r.write(out); } Synchronization is needed to ensure

I'm trying to learn how to pause and resume a thread in java. I'm using an Applet that implements Runnable has 2 buttons "Start" and "Stop". public void init(){ th = new Thread(this); th.start(); btn_increment = new Button("Start"); btn_increment.addActionListener(new ActionListener(){ public void actionPerformed(ActionEvent ev){ th.notify(); } }); add(btn_increment); btn_decrement = new Button("Stop"); btn_decrement.addActionListener(new ActionListener(){ public void actionPerformed(ActionEvent ev){ try{ th.wait(); } catch(InterruptedException e) { e.printStackTrace(); } } }); add(btn

I've got a rather large SQL Server 2005 database that is under constant development. Every so often, I either get a new developer or need to deploy wide-scale schema changes to the production server. My main concern is deploying schema + data updates to developer machines from the "master" development copy. Is there some built-in functionality or tools for publishing schema + data in such a fashion? I'd like it to take as little time as possible. Can it be done from within SSMS? Thanks in advance for your time I suggest using RedGate's tools (this is not advertisment, but real life experience

First, I am aware that the mutexes are not considered async-safe normally. This question concerns the use of sigprocmask to make mutexes safe in a multithreaded program with async signals and signal handlers. I have some code conceptually like the following: struct { int a, b; } gvars; void sigfoo_handler(int signo, siginfo_t *info, void *context) { if(gvars.a == 42 || gvars.b == 13) { /* run a chained signal handler */ } } /* called from normal code */ void update_gvars(int a, int b) { gvars.a = a; gvars.b = b; } gvars is a global variable which is too large to fit in a single sig_atomic_t .

I have written an assembly which is integrated in sql server, providing some stored procedures written in C#. The assembly has a readonly static variable holding some configuration data. This data is manipulated via stored procedures, which are also provided by the assembly. Obviously I have to synchronize access to this static variable. I tried to use lock(someGuard) { // ... access static configuration } inside my configuration class. But then I get a HostProtectionException, telling me, that the assembly has to run with full trust to do that. Is there a better way to do that? There is

I'm looking at some code in a third party library that contains a synchronized method, and within this method there is a synchronized block that locks on an instance variable. It's similar to this: public class Foo { final Bar bar = new Bar(); public synchronized void doSomething() { // do something synchronized(bar) { // update bar } } ... } Does this make sense? If so, what benefits are there to having a synchronized statement within a synchronized method? Given that a synchronized method locks on the entire object, it seems redundant to me. Perhaps this approach makes sense when working