1
NXPTM M522XX, KINETIS and i.MX RT / Re: [MCF52235] - TCP Client - Multiple Connect/Disconnect memory problem.
« on: July 04, 2008, 07:08:48 PM »
Hi Mark
Thanks for your suggestions my friend. Your are always helping people out. So when do you really work?
After a hard debug session i could realize what i need was a fast flush of the allocated socket more than i ever needed in life!!! So after being slapped on face many times by the stack, i could finally achieve the perfect desired behavior by making the socket LINGER !!! This immediately flushes all socket data, buffers and whatever it takes from RAM by calling m_close. Since the client is the one who will finish the session when it get´s what´s needed, making it´s socket linger incredibly reduces the time between multiple connect/disconnect actions, and is just what i needed to run my pooling thing!!!
Thanks for your suggestions my friend. Your are always helping people out. So when do you really work?
After a hard debug session i could realize what i need was a fast flush of the allocated socket more than i ever needed in life!!! So after being slapped on face many times by the stack, i could finally achieve the perfect desired behavior by making the socket LINGER !!! This immediately flushes all socket data, buffers and whatever it takes from RAM by calling m_close. Since the client is the one who will finish the session when it get´s what´s needed, making it´s socket linger incredibly reduces the time between multiple connect/disconnect actions, and is just what i needed to run my pooling thing!!!