updates.

[silc.git] / TODO

diff --git a/TODO b/TODO
index c8d44d4e1b356ebcff699e6aab9ea153d77b210a..7e52a12a5aea3d05ab3ba58e2a2f68676c81b079 100644 (file)
--- a/TODO
+++ b/TODO
@@ -45,17 +45,11 @@ TODO/bugs In SILC Server
 
        o Add rehashing support.
 
- o Assure that server is allowed to connect only once to router.  Meaning
-   if server connection is established already, same connection cannot be
-   established again.
-
  o If server send CUMODE_CHANGE notify (like setting founder) to router
    and router does not have founder on channel (founder is left or there's
    no founder on channel at all), the router will accept the server's
    founder mode change, even though it perhaps should not do that.
 
- o Make the normal server save user counts with LIST command reply.
-
  o The router should check for validity of received notify packets from
    servers (after all buggy servers may send notify that is actually
    something that should have not been sent).
@@ -89,12 +83,14 @@ TODO/bugs In SILC Libraries
  o Rewrite the lib/silcsim/silcsim.h.  The SilcSimContext should be
    private and silc_sim_alloc should take necessary arguments.
 
- o lib/silcsftp/sftp_fs_memory.c use directly open(), close() etc. 
-   routines.  Change to use silc_file_* routines.
-
  o SILC RNG does not implement random seed files, and they should be
    implemented.
 
+ o The SilcSocketConnection in the SFTP interface is actually redundant
+   and should perhaps be removed.  The application can save it in the
+   context it provides, which is delivered by SFTP libary to all 
+   callback functions.
+
 
 TODO in Toolkit Documentation
 =============================
@@ -102,18 +98,18 @@ TODO in Toolkit Documentation
 Stuff that needs to be done in order to complete the Tooolkit Reference
 Manual.
 
- o Lots of ROBOdoc header formatting is undone in lib/silcske, 
-   lib/silcutil, and lib/silccrypt.
+ o Lots of ROBOdoc header formatting is undone in lib/silcutil, and 
+   lib/silccrypt.
 
  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).
+   it (how to link etc), debugging, architecture, types, etc.
 
- o Write "Programming conventions" document to describe the coding
-   and naming conventions used in the Toolkit (should not be 
-   actually the CodingStyle document, but something more general).
+ o Write "Platform Implementations" document to describe what platforms
+   Toolkit support, what has been implemented, what has not been, what
+   wors differently etc.
 
 
 TODO in SILC Protocol