site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com None so far. I'm just planning for the worst-case. joe _______________________________________________ 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... If you issue an RFCOMM write call, the data will be delivered unless the connection is terminated. Unless there are horrible radio conditions, it seems unlikely to take very long before the write completes and you callback is called. Are you having specific problems with writes taking too long to complete? In answer to your question, your best bet is probably to create an NSTimer with the timeout that you want. Then in your callback, yoou can invalidate the timer if it hasn't fired. With that model, there is no need to block your main thread. Either the timer will fire, or you will get your write callback called. Thanks. I'm still deciding exactly how to arrange my code. I'm in a bind that I must design my bluetooth code to plug into a cross platform application that's expecting a particular interface and also be exported as a bundle that's loaded into a CFM application. This email sent to site_archiver@lists.apple.com