site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com User-agent: www.mail386.com Jason,

you should probably implement a data receive timer in your app, and if you don't receive any data and your timeout, then just close the connection on OBEXSession. OBEX doesn't really have a notion of timeouts, so there is no API that can help you there.

I did that and it works as expected. So, "automatic timeouts" are only possible using low-level BT connections?

you should do all Bluetooth from whatever thread the first Bluetooth command is send from. I suggest you stick with doing everything from the main thread if possible, you will have the most success doing it that way.

Doing BT stuff single threaded is giving me problems though. Designing multi-threaded applications is much simpler. Are you sure I can't do it multi-threaded? Regrads, 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