[Nym3-commit] r254 - trunk/nym3

[laurent at conuropsis.org]

Author: laurent
Date: 2005-05-07 18:59:48 +0200 (Sat, 07 May 2005)
New Revision: 254

Modified:
   trunk/nym3/TODO
Log:
Update TODO items.


Modified: trunk/nym3/TODO
===================================================================
--- trunk/nym3/TODO	2005-05-07 16:04:59 UTC (rev 253)
+++ trunk/nym3/TODO	2005-05-07 16:59:48 UTC (rev 254)
@@ -1,4 +1,4 @@
- $Id$
+$Id$
 
 Legend:
         - Not done
@@ -8,47 +8,24 @@
         D Deferred
         X Abandoned
 
-Notes:
- - In case something brakes, remember it's emag's fault.
- - Use clean_surbs after sending something through mixminion
+ - rewrite clean_surbs, and use it once in a while in the server.
+ - periodically scans for emails that need to be relayed [server]
+ - be careful about control message nonce reuse [client]
+ - something is broken somewhere about bitfield manipulation
+ - use `email' lib to fiddle with an email to relay [server]
 
 doc:
  - add doc strings in __init__.py in every module.
 
 Message.py:
- - add the print method which prints the content of a command object in a user
+ X add the print method which prints the content of a command object in a user
    friendly form
- - do further testing once we start using the commands in the client/server
- . test the parser
- o add the __str__ method which outputs the message ready to be
-   sent
- o add the CommandSToC 
- - delete expired surbs.
- - periodically scans for emails that need to be relayed.
 
 Common.py:
  - move lifecycle to somewhere in the server, since the client should not use 
- it
+   it
 
 Mail.py:
  - Check whether oldestMid is well situated. (Shouldn't it be in Commons, or 
  anyplace in the server module) In fact all the Mail.py module should go
  in the server. Lolo : your module, your call :)
-
-Client.Main:
- - Obviously, not much was done. Specify scenarios and write the parser +
- empty functions that are supposed to do the work. Take a look at nickm's API
- before doing that.
-
-Client.User:
- - Look at the tag class. It was supposed to provide a nice shortcut for a user
- to identify his accounts. But it might be just some dirty hack. Ignore it
- to begin with, propose a nicer solution if type the whole account name is too
- troublesome
-
-JR:
- o look at the crypto module of mixminion
- o what is the format of the keys
- o implement encrypt a mail, a set of synopses
- - implement sign a control message
- o figure what the routing type and info (cf Command relay) are