updates.

[silc.git] / TODO

diff --git a/TODO b/TODO
index 5842ba8918598d1e7315168152c3eaa9d6827ea5..92212fa4f6aed90fdd69144a297979b01556c5f3 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,14 +1,6 @@
 TODO for Irssi SILC Client 1.0
 ==============================
 
- o bugs parsing nicknames with @ in NICK_CHANGE.
-
- o UTF-8 decode WHOIS userinfos, topic, etc.
-
- o c0ffee's MIME signal
-
- o SILC protocol version 1.2 integration
-
  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,14 +9,15 @@ TODO for Irssi SILC Client 1.0
 TODO for SILC Server 1.0
 ========================
 
- o WHOIS search by public key in attrs.
+ o Check that +of works correctly when same client is +of already on
+   some other server on same channel.
 
- o Backup router related issues:
+ o Check that founder key is distributed ok during backup resuming.
 
-       o Add special handling in router and server for "connection
-         timed out" error.  Be optimistic.
+ o Check that getting MOTD from other servers works.
 
- o SILC protocol version 1.2 integration
+ o invite (with @server!*@host) not working from normal server/backup
+   router?
 
  o Testing
 
@@ -32,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).