[tor-commits] [gettor/master] Changed log format in 'Design'. Added section 'Features'. Deleted stuff from 'Discussion' and added some others.

[ilv at torproject.org]

commit 623b5bf370a97d823127242464f66750ac1a97ca
Author: ilv <ilv at users.noreply.github.com>
Date:   Fri Jun 20 20:54:28 2014 -0400

    Changed log format in 'Design'. Added section 'Features'. Deleted stuff from 'Discussion' and added some others.
---
 spec/design/core.txt |   47 +++++++++++++++++++++--------------------------
 1 file changed, 21 insertions(+), 26 deletions(-)

diff --git a/spec/design/core.txt b/spec/design/core.txt
index cc7b05d..4c180d6 100644
--- a/spec/design/core.txt
+++ b/spec/design/core.txt
@@ -1,8 +1,12 @@
    Google Summer of Code 2014 GetTor Revamp - Core module
    Author: Israel Leiva - <israel.leiva at usach.cl, ilv at riseup.net>
-   Last update: 2014-06-06
-   Version: 0.03
-   Changes: [0.03]
+   Last update: 2014-06-20
+   Version: 0.04
+   Changes: [0.04]
+            Changed log format in 'Design'
+            Added section 'Features'
+            Deleted stuff from 'Discussion' and added some others
+            [0.03]
             Changed proposed format for link files to RFC 882 (ConfigParser).
             Read configuration from file with ConfigParser.
             [0.02]
@@ -50,7 +54,11 @@
    
       * logs/: Directory for logs. Should be specified on gettor.cfg
    
-         ----- core_yyyy-mm-dd.log: daily log of requests.
+         ----- all.log
+         ----- info.log
+         ----- debug.log
+         ----- warn.log
+         ----- error.log
    
       * Core module of GetTor.
    
@@ -125,30 +133,17 @@
    f. get_links() returns the message previously constructed.
    g. The SMTP service creates a message with the links obtained and 
       send it to the user.
-   
+
 5. Discussion
-   
-5.1 On demand generation 
 
-   Now we consider links generation over a period of time, say, once a week.
-   Generating links on demand don't seem to be necessary and it would 
-   certainly be resource consuming. The core module doesn't care about
-   how links are generated, it just assumes they exist. Is there any case
-   where on demand link generation should be considered?
+5.1 Daily logs
 
-5.2 Core class
-    
-    Should the Core be a module on its own, or a class of GetTor? 
-    Currently it's just a class, after realizing that
-    
-    core = gettor.core.core()
-    
-    Was too much. It's better to do
-    
-    core = gettor.Core()
-    
-    Isn't?
+   Currently, logs are separated by level of information (debug, info, error).
+   Is it necessary to do this by days/weeks too?
+   
+6. Features
 
-5.3 Logs
+   Possible features to be added in the future (open to discussion)
+   
+   a. Send HTTP links (currently some official mirrors are HTTP only). 
 
-   Should we mantain separate logs for successful and fail requests?