site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=j3lAxcmUdnbKp2Au7FkO9XHXj0EN3Up5L2z5JO+QTiU=; b=eBqgltoPoVmEtl/dj5yuuyhQ4i7e7T1r6vXPJ5tf6vaaI12gW6QqlcFe9pYagecPc0 EjbyhFdL6i6Ia9hjFF65OSSgZrHWEZGO+2/0TjWBbnGk8BSoV/2mk2R8wo6shytVKFZM 2LUrXBszAkAL0MOrbk3x5ZU+1i9oRAFoDaong= Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=mBxxMNXydmcFGaaR8cGB1Fxzd0WWOSDtXITm9lTQBx2T+XCLBDCrMNujQgFbXXdoj3 9I8O58wZDW50NlDOLMCYBdDhF6b+CCemY9BjNqGH2TmUztk8dWu81j34QwWlm0W+PHuC wCw3/Bmvcer6D9tAHvQDaKwz+f/CCxv4ofkdM= I happened to use the IOBluetooth C API in a project some time ago and I only discovered that all bluetooth functions have to be called from the same thread, but not explicitely the main thread. I currently have no access to Snow Leopard but did that also change in the new release? When I developed the code I noticed that some notifications are sent to the current thread but especially the "ConnectionClose" notifications where always sent to the thread that I used to open the first connection. Since this was never the main thread, I put all the bluetooth stuff in a separate worker thread and everything worker fine. Has anyone tested this in the new Mac OS release? Do I have to change the code? David Herrmann _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com