site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com User-agent: www.mail386.com Jason,
sorry for the late reply, I don't know how I missed this message.
No problem, if I was in a hurry I would repost this message. :)
timeouts are only supplied by lower-level functions. the other app might just be waiting for something, and not sending you data. e.g. OBEX Browsing - the user is just staring at the directory, and not clicking anything. no data is sent in this case. choosing a timeout in this case is not relevant. thus, timeouts are left to an exercise to the user of the OBEX Session.
I have thought that much.
you can do your app multi-threaded, just make sure you do ALL Bluetooth related activities on the first thread from which you call anything in the Bluetooth stack. Bluetooth is not threadsafe. we recommend you doing it from the main thread, especially if you are doing Bluetooth UI of any kind.
Actually I thought designing BT stuff single-threaded is harder than multi-threaded, though seeing that I must do discovery, SDP query and OBEX transfer sequentially and not simultaneously, I don't think it's hard now. I will just set up a timer that will act as sort of scheduler - stop the connection (if it is going nowhere) or start the connection when a connection slot is available (I can't do more than 7 connections at a time). Thank you, Boris ___________________________________________________________________________ Najhitrejši brezplačni klicni dostop :: Varno in zanesljivo po internetu Obiščite http://www.dialup386.com/ _______________________________________________ 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