updates.

[silc.git] / TODO

diff --git a/TODO b/TODO
index 7ed56659ea7521b3930089779c6844db05725c20..92212fa4f6aed90fdd69144a297979b01556c5f3 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,14 +1,6 @@
 TODO for Irssi SILC Client 1.0
 ==============================
 
- o Support to set arbitrary pulic key in CMODE.
-
- o INVITE/BAN by public key file.
-
- o Signed message payload handling on UI
-
- o bugs parsing nicknames with @ in NICK_CHANGE
-
  o Testing - See test plan:
      http://silcnet.org/docs/silc-client-1.0-test.pdf
      http://silcnet.org/docs/silc-client-1.0-test.ps
@@ -17,7 +9,15 @@ TODO for Irssi SILC Client 1.0
 TODO for SILC Server 1.0
 ========================
 
- o 1.2 backup router support
+ o Check that +of works correctly when same client is +of already on
+   some other server on same channel.
+
+ o Check that founder key is distributed ok during backup resuming.
+
+ o Check that getting MOTD from other servers works.
+
+ o invite (with @server!*@host) not working from normal server/backup
+   router?
 
  o Testing
 
@@ -25,29 +25,22 @@ TODO for SILC Server 1.0
 TODO/bugs In SILC Libraries
 ===========================
 
- o WIN32 silc_net_create_connection_async does not work the same way
-   than on Unix.  Do it with threads on WIN32.  The function works but
-   is not actually async currently (Fix this to 0.9.x).
+ o Test cases for all payload encoding and decoding routins in lib/silccore/
+
+ o Test cases for math library routines in lib/silcmath/
 
 
 TODO in Toolkit Documentation
 =============================
 
-Stuff that needs to be done in order to complete the Tooolkit Reference
+Stuff that needs to be done in order to complete the Toolkit Reference
 Manual (Do these to 0.9.x).
 
- o Document the "notify" and "command_reply" client operations variable 
-   argument lists for all possible notify types and command replys.
-
  o Write "Programming with Toolkit" document, describing how to build
    Toolkit, how the build system works, where is everything, how
    new (external) projects can be glued into Toolkit (use irssi as an
    example), and how external projects can use Toolkit without gluing into
    it (how to link etc), debugging, architecture, types, etc.
 
- o Write "Platform Implementations" document to describe what platforms
-   Toolkit support, what has been implemented, what has not been, what
-   works differently etc.
-
- o Searching of predefined keywords, exact and partial matches (would be 
+ o Searching of predefined keywords, exact and partial matches (would be
    nice).