Merged silc_1_0_branch to trunk.

[silc.git] / lib / silcclient / client_ops_example.c

diff --git a/lib/silcclient/client_ops_example.c b/lib/silcclient/client_ops_example.c
index 19b9acc14fdc856291da82e83f43c54b5f13938e..7c03f1c49cde424de92cb0a9e11b55e74696fdb9 100644 (file)
--- a/lib/silcclient/client_ops_example.c
+++ b/lib/silcclient/client_ops_example.c
@@ -5,7 +5,9 @@
 
    At the end of this file SilcClientOperation structure is defined, and
    it is the one the you will give as an argument to the silc_client_alloc
-   function. See also lib/silcclient/README file, and silcclient.h. */
+   function. See also lib/silcclient/README file, and silcclient.h.
+
+   You may freely use this file in your application. */
 
 
 /* Message sent to the application by library. `conn' associates the
@@ -31,15 +33,16 @@ silc_say(SilcClient client, SilcClientConnection conn,
 static void
 silc_channel_message(SilcClient client, SilcClientConnection conn,
                     SilcClientEntry sender, SilcChannelEntry channel,
-                    SilcMessagePayload payload, SilcMessageFlags flags,
-                    const unsigned char *message, SilcUInt32 message_len)
+                    SilcMessagePayload payload, SilcChannelPrivateKey key,
+                    SilcMessageFlags flags, const unsigned char *message,
+                    SilcUInt32 message_len)
 {
 
 }
 
 
 /* Private message to the client. The `sender' is the sender of the
-   message. The message is `message'and maybe NULL.  The `flags'  
+   message. The message is `message'and maybe NULL.  The `flags'
    indicates message flags  and it is used to determine how the message
    can be interpreted (like it may tell the message is multimedia
    message). */