updates

diff --git a/CHANGES b/CHANGES
index 98e2f3ac6dde5c5013dba749007c78d4269c1f5c..9003d86fc38cf5dee940ee92e6ad236e0d01e590 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,47 @@
+Tue Nov 21 19:49:31 EET 2000  Pekka Riikonen <priikone@poseidon.pspt.fi>
+
+       * silc_server_replace_id now broadcasts the received replace ID
+         packet if it is not broadcast packet already. The router must
+         broadcast to inform other routers about changed ID.
+
+       * Added backpointer to server's router into SilcServer context in
+         silcd/server_internal.h.
+
+       * Fixed silc_server_packet_broadcast to send correct broadcast
+         packets.
+
+       * The channel key is now distributed to the local client as soon
+         as it is received from the router (in router environment) so that
+         no other packet may be sent for the channel until client has 
+         received the key.
+
+       * silc_server_remove_channel_user now broadcasts the received
+         Remove Channel User packet if it is not broadcast packet already.
+         The router must broadcast to inform other routers about removed
+         channel user.
+
+       * Added users field into SilcPacketContext that is a reference count
+         of the context.  One can increase the reference count by calling
+         silc_packet_context_dup which is now changed to just increase the
+         reference count instead of duplicating the data.  The reference
+         count is decresed by calling silc_packet_context_free that will
+         free the data after the reference count hits zero.
+
+         For now on the packet context and everything allocated into it
+         (including the raw packet from network) must be freed by calling
+         the new silc_packet_context_free function.  Added also new function
+         silc_packet_context_alloc that must be used now to allocate the
+         context.  This also means that if a routine is asynchronous from
+         silc_[client/server]_packet_parse_type the packet context must
+         be duplicated by calling silc_packet_context_dup.  Otherwise it
+         gets free'd after silc_[client/server]_packet_parse_type returns.
+         Also, one must remember that if packet is duplicated then its 
+         reference count must be decresed by calling the free function as
+         many times as it was duplicated.
+
+       * Changed SilcBuffer field from protocol contexts to SilcPacketContext
+         from both client and server.
+
 Mon Nov 20 23:47:03 EET 2000  Pekka Riikonen <priikone@poseidon.pspt.fi>
 
        * Made joining to a channel working in router environment.

diff --git a/doc/draft-riikonen-silc-pp-01.nroff b/doc/draft-riikonen-silc-pp-01.nroff
index bc7e8a515e3d93f5910b88116f8dd21b5737b878..e94eb9952b8bfb1cfa5af7c12eae32ac2513b3dd 100644 (file)
--- a/doc/draft-riikonen-silc-pp-01.nroff
+++ b/doc/draft-riikonen-silc-pp-01.nroff
@@ -729,7 +729,7 @@ List of SILC Packet types are defined as follows.
           that is indirectly connected to the sender.
 
           When received, the server or router must distribute
-          SILC_NOTIFY_TYPE_LEAVEW to local clients on the channel.
+          SILC_NOTIFY_TYPE_LEAVE to local clients on the channel.
 
           Payload of the packet:  See section 2.3.26 Remove Channel User
                                   Payload
@@ -1028,8 +1028,7 @@ Notify payload is used to send notify messages.  The payload is usually
 sent from server to client, however, server may send it to another
 server as well.  This payload may also be sent to a channel.  Client must
 not send this payload.  The receiver of this payload may totally ignore the
-contents of the payload, however, notify message should be noted and
-possibly logged.
+contents of the payload, however, notify message should be audited.
 
 The payload may only be sent with SILC_PACKET_NOTIFY packet.  It must
 not be sent in any other packet type.  Following diagram represents the