Dear Patrick,
Thanks so much for your reply!
I ever believed that TCP protocols handle everything on the connection. Only
UDP needs a lot of work to manage the connection. According to your
description, it is not like that?
I have not worked on a so low level network programming. Your email help
Dear Patrick,
Thanks so much for your answer!
I don't know the details of TCP. However, TCP should be a reliable protocol.
Developers are not required to keep its connection state since TCP does
that. That's one of the important differences between TCP and UDP, right?
When using UDP, it is mandat
Dear all,
Can anyone answer this question?
Thanks so much!
Bing
On Fri, Apr 29, 2011 at 7:21 PM, Bing Li wrote:
> Dear Michael,
>
> "Disgracefully" means the client does not close normally. It might be
> crashed or closed by killing the relevant thread or process. I did that by
> clicking the
Dear Michael,
"Disgracefully" means the client does not close normally. It might be
crashed or closed by killing the relevant thread or process. I did that by
clicking the red Tasks button in XCode. In this situation, the connection
must not be closed properly with the socket methods.
According t
>
> I started to use CocoaAsyncSocket to establish TCP connections among iPads.
>
> I got a problem. According to the references (
> http://code.google.com/p/cocoaasyncsocket/wiki/Reference_AsyncSocket),
> onSocketDidDisconnect would be invoked immediately if the connection is not
> already disco
Dear all,
I started to use CocoaAsyncSocket to establish TCP connections among iPads.
I got a problem. According to the references (
http://code.google.com/p/cocoaasyncsocket/wiki/Reference_AsyncSocket),
onSocketDidDisconnect would be invoked immediately if the connection is not
already disconnec
