--
Sent from my mobile phone
(please excuse any mistakes or short response I might have made)
> --
> You received this message because you are subscribed to the Google Groups "CocoaAsyncSocket" group.
> To post to this group, send email to cocoaasy...@googlegroups.com.
> To unsubscribe from this group, send email to cocoaasyncsock...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/cocoaasyncsocket?hl=en.
>
--
Sent from my mobile phone
(please excuse any mistakes or short response I might have made)
Or something like that. That's the gist of what the engineers on the Dev Forums said.
--
Sent from my mobile phone
(please excuse any mistakes or short response I might have made)
On Oct 14, 2010, at 5:44 PM, Shukuyen <shuk...@googlemail.com> wrote:
> Yup you know what causes the problem and how to fix it? Care to
> share? :-)
>
> Thanks!
>>> For more options, visit this group athttp://groups.google.com/group/cocoaasyncsocket?hl=en.
Somewhat related: I am under the impression that apple doesn't expose an API to interact with Bluetooth on iOS. I could be wrong though...
--
Sent from my mobile phone
(please excuse any mistakes or short response I might have made)
-Robbie Hanson
I think we need to find a way to use CocoaAsyncSocket without turning
Bluetooth off.
Richard Fink
1160 Mission St, #2108
San Francisco, CA 94103
Tel: 415.409.6396
Cell: 415.302.7317
Skype: richardfink
Twitter: @ricfink
Jim Geldermann
-Robbie Hanson
--
Sent from my mobile phone
(please excuse any mistakes or short response I might have made)
Thanks.
Richard Fink
1160 Mission St, #2108
San Francisco, CA 94103
Tel: 415.409.6396
Cell: 415.302.7317
Skype: richardfink
Twitter: @ricfink
-----Original Message-----
From: cocoaasy...@googlegroups.com
[mailto:cocoaasy...@googlegroups.com] On Behalf Of Robbie Hanson
Sent: Friday, October 15, 2010 9:03 AM
To: cocoaasy...@googlegroups.com
Subject: Re: iPhone losing wifi after AsyncSocket writeData
You can achieve this by binding the socket (invoking bind()) before starting the connect process.
The bind method is generally considered to be for server use. You bind a socket to a specific port (e.g. port 80 for HTTP servers). But bind takes both an interface and a port. If the interface is left "blank" then the socket will use any interface. And likewise, if the port is left "blank" then the socket will use any available port.
So for outgoing client connections, one could bind the socket the a specific interface, while still allowing the socket to pick any available port upon connection (as typically happens).
> May I ask you to post some code to make it clearer ?
I've committed the new method in revision 101. I also added a sample iPhone xcode project named "InterfaceTest".
It demonstrates the new client method that allows you to specify which interface to use.
The project gives sample code demoing how one might specify the WiFi or 3G/cell interface.
Let me know if you have any questions.
I'll try to put up more general information concerning interfaces and the AsyncSocket interface options on the wiki later this week.
-Robbie Hanson
-Robbie Hanson
-Robbie Hanson
I too would still see the wifi status bar showing signal, but wifi would not
work through any app on the device, not just mine.