Lines Matching full:callback
32 * to connect, and a callback to invoke on connection events.
36 * The main job on the client side falls on the client's callback routine that
38 * will invoke that callback to report current connection status.
40 * In general, there are three connection events passed to the callback:
45 * Typically, when client's callback is called for a successful connection, the
49 * When client's callback is invoked with an error (ASIO_STATE_FAILED event), the
52 * by returning ASIO_ACTION_RETRY from the callback. If client returns ASIO_ACTION_ABORT
53 * from the callback, the connector will stop connection attempts, and will
54 * self-destruct. If ASIO_ACTION_RETRY is returned from the callback, the connector
58 * When client's callback is invoked with ASIO_STATE_RETRYING (indicating that
72 /* Declares callback that connector's client uses to monitor connection
92 * cb, cb_opaque - Callback to invoke on connection events. This callback is
100 * will destroy its descriptor after client's callback routine returns with a
128 * Note that connection result will be reported via callback set with the call to
138 * This routine should be called from the connection callback on successful
