site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com Joseph K. On Apr 2, 2007, at 4:50 PM, Daniel Birns wrote: Fellow Bluetoothers, Thanks. --Daniel _______________________________________________ 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/joeman%40mac.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... I'm not sure where the MTU gets set -- whether it's in the spec or is determined by the particular interface, etc? Either way, my code breaks up its outgoing packets into MTU sized chunks and I've had no problem at all with writing to my device on many different Macs with many different bluetooth interfaces. I'm using Carbon and RFCOMM, and the GetMTU() call is telling me that my mtu is 128 bytes, and in fact the WriteAsync() call fails when I write more than that, and succeeds when I write less, as advertised. This seems like a very small MTU. Is there some way to make it bigger? This email sent to joeman@mac.com This email sent to site_archiver@lists.apple.com