Socket issue about cocos2dx-better HOT 4 CLOSED

if you need send data immediately, call flush after sendData, or call CCTCPSocketHub::sendPacket, it will flush.

from cocos2dx-better.

about another issue, maybe you are right, the socket code is very new and I may rafactor them a bit

from cocos2dx-better.

I think there is something wrong in

if(m_outBufLen + size > kCCSocketOutputBufferDefaultSize) {
flush();
if(m_outBufLen + size > kCCSocketOutputBufferDefaultSize) {
destroy();
return false;
}
}

if flush() dose not send anything,it may occur EINPROGRESS or EAGAIN, and the socket would destroyed. I have an idea that use a list instead of m_outBufLen ,and the element of list is a single buf,when flush() dose not send anything or send part of buf,it can be sent next time.your opinion？Thanks!

from cocos2dx-better.

your solution is allocating more memory to hold data, so why not directly enlarge out buffer? Or, just change kCCSocketOutputBufferDefaultSize to a bigger number.

However, I don't know when can a flush() fail, maybe in a terrible situation. Something must be wrong if a flush can fail. So I don't think destroy is a overreaction for flush failure.

from cocos2dx-better.