hi. i have a problem with tizen application about socket.io-client-cpp HOT 3 CLOSED

Seems like your code reaches to the end too early, where triggers the destructor of the sio::client, which will call sync_close as well.
Try to block your execution some where.

from socket.io-client-cpp.

So I wrote a while statement at the end of the source code.
(Line number:143 https://github.com/Francis0121/nornenjs_v3/blob/master/client-tizen-socket-io/src/socket_io_client.cpp)
Like this, i can use socket event bind.

But when I close my tizen application, client does not close. At the same time server is dead.
How can i call sio::client destructor in the main loop?

And I'd like to know about your library design architecture in Ios Application.

from socket.io-client-cpp.

1. please use debug mode to start your server

DEBUG=* node index.js

See what's happened when your server is dying.

Usually OS will close the physical connection for terminated applications. So your problem is Server do not know client is closed rather than client does not closed. Client is actually closed, but server do not know that. It will also happen if your application is abnormally terminated or network is drop.

If you want server to know when client is closed, please make sure to call client.sync_close() once you detect your application is exiting.

Also, It is important to have some defensive code in the server side to deal with the case that client is drop without notification.

2. You can refer to the iOS demo
   https://github.com/socketio/socket.io-client-cpp/tree/master/examples/iOS

from socket.io-client-cpp.