evpp | developing high performance network services | HTTP library

It depends. Binding a reference to a local object (the shared pointer in this case) into a function object works if the lifetime of the referred object exceeds the lifetime of the callback funtion. Relying on such assumption is less safe in the sense that if the assumption is made by mistake, the behaviour of the program will be undefined.

In many cases where calls to the callback are asynchronous, such assumption cannot be made.

For what it's worth, I severely dislike std::bind. I always use a lambda. This might work:

Like in any network-programming, when a client sends a request to the server, the server responds with a response. But for this to happen the following conditions must be met

1. The server must be UP and running
2. The client should be able to make some sort of connection between them
3. The connection should not break while the server is sending the response to the client or vice-versa

But in case of a message queue, whatever the server wants to tell the client, the message is placed in a message-queue i.e., separate server/instance. The client listens to the message-queue and processes the message. On a positive acknowledgement from the client, the message is removed from the message queue. Obviously a connection has to made by the server to push a message to the message-queue instance. Even if the client is down, the message stays in the queue.

I asked my problem in Github. Please refer to the following page for the answer. Issue Solved