This interface defines the SILC Client Library API for the application.
 The Client Library is a full featured SILC client without user interface.
 A simple interface called SILC Client Operations (SilcClientOperations)
 is provided for applications to implmeent the necessary functions to use
 the client library.  The silcclient.h header file includes client library
 API, such as command handling and message sending.  The silcclient_entry.h
 header file includes entry handling, such as channel and user entry
 handling.

 Practically all functions in the Client Library API accepts SilcClient
 and SilcClientConnection as their first two argument.  The first argument
 is the actual SilcClient context and the second is the SilcClientConnection
 context of the connection in question.  Application may create and handle
 multiple connections in one SilcClient.  Connections can be created to
 servers and other clients.

 The Client Library support multiple threads and is threads safe if used
 correctly.  Messages can be sent from multiple threads without any
 locking.  Messages however are always received only in one thread unless
 message waiting (see silc_client_private_message_wait as an example) is
 used.  The threads can be turned on and off by giving a parameter to the
 SilcClient.  When turned on, each new connection to remote host is always
 executed in an own thread.  All tasks related to that connection are then
 executed in that thread.  This means that client operation callbacks for
 that connections may be called from threads and application will need to
 employ concurrency control if the callbacks need to access shared data
 in the application.  Messages are also received in that thread.