[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Unfortunately for the user, the ALSA client crashes. The server detects
that the client has disconnected, and puts the client on a list of lost
clients for the project. The user then starts another copy of the client,
which connects to the server in the same way it did before. This time,
however, the server checks through the list of lost clients and finds that
the class of the new client matches the class of the lost client and so it
resumes the lost client using the new one. It gives it the 128-bit ID of
the lost client, adds it to the project, and then sends a
CCA_Restore_Data_Set
event to the client. The client then cleans
itself up, ready to recieve the data set. The server sends the client the
configs, and then another CCA_Restore_Data_Set
event. The client
recieves this data and its state has been restored that of the client that
crashed.
The user can stop this behaviour by specifying the `--ladcca-no-autoresume' option on the client's command line.