• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: IOBluetoothRFCOMMChannel and memory management
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: IOBluetoothRFCOMMChannel and memory management


  • Subject: Re: IOBluetoothRFCOMMChannel and memory management
  • From: Peter Sichel <email@hidden>
  • Date: Thu, 24 Sep 2009 08:21:26 -0400


On Sep 24, 2009, at 6:21 AM, Hugh Cole-Baker wrote:

I am writing an application that communicates using an RFCOMM channel to a mobile phone. I use the openRFCOMMChannelAsync:withChannelID:delegate: method of IOBluetooth device to open the channel. The docs for this method state "The RFCOMM channel object is already retained when this function returns success; the channel must be released when the caller is done with it" so I don't retain the object from my code while using it.

Apple's sample code (RFCOMM_Open_SPP_Example) does retain the rfcomm channel object
upon a successful return from - [openRFCOMMChannelAsync:withChannelID:delegate], so
I suspect the documentation is outdated.


- Peter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >IOBluetoothRFCOMMChannel and memory management (From: Hugh Cole-Baker <email@hidden>)

  • Prev by Date: IOBluetoothRFCOMMChannel and memory management
  • Next by Date: Panic in Bluetooth stack on 10.6.1 ?
  • Previous by thread: IOBluetoothRFCOMMChannel and memory management
  • Next by thread: Panic in Bluetooth stack on 10.6.1 ?
  • Index(es):
    • Date
    • Thread