gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] journals hemppah


From: Hermanni Hyytiälä
Subject: [Gzz-commits] journals hemppah
Date: Fri, 01 Aug 2003 08:35:57 -0400

CVSROOT:        /cvsroot/fenfire
Module name:    journals
Branch:         
Changes by:     Hermanni Hyytiälä <address@hidden>      03/08/01 08:35:57

Modified files:
        .              : hemppah 

Log message:
        last few days

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/journals/hemppah.diff?tr1=1.26&tr2=1.27&r1=text&r2=text

Patches:
Index: journals/hemppah
diff -u journals/hemppah:1.26 journals/hemppah:1.27
--- journals/hemppah:1.26       Mon Jul 28 06:05:17 2003
+++ journals/hemppah    Fri Aug  1 08:35:56 2003
@@ -51,35 +51,47 @@
 August
 ------
 
-2003-8-9-2003-8-23: vacation    
+- read IBC-based signature schemes
+
+2003-08-09-2003-08-23: vacation    
       - 2003-8-17 - 2003-8-24: the island of Samos, Greece
+      
+2003-08-04 - 2003-08-08
+   - test running Tapestry/Sandstorm with java.nio
+   - test running Tapestry/Sandstorm with kaffe (latest cvs version)
+   - ask MLDonkey programmers: how hard it would be to use 
+     MLDonkey's DHT routing mechanism separately
+   - ask Ben Zhao (Tapestry project leader): fix Perl script which
+     fail to draw graph with gnuplot (simbench)
+       
 
-July
-----
+=============
+Past:
+=============
 
-   - Work for Storm with benja:
-     1) Can we really use Tapestry with benja (discuss with Benja)
-     2) Write a straightforward text about how Storm would work with
-        Tapestry
-       - Pseudocode: how Storm would use Tapestry's services (implementation)
-     3) Work with mudyc and benja: FenPDF's data storing
-     4) If there is time remaining: think merge techniques for FenPDF's
-        RDF data
-       
-- read IBC-based signature schemes
-       
-       
-2003-06-17 -
+2003-07-29-2003-08-01
 
+    - Storm's PEG reformatting for navidoc compatibility (that I have created) 
+    - avalaible overlays PEG: editing based on benja's comments
+    - RDF reading:
+      - W3.org's RDF documents
+      - RDF-related PEGs
+      - RDF/Ontology version management (paper: "Ontology Versioning and 
Change 
+        Detection on the Web")
+      - think little versioning and merge
+    - read more Fenfire's other PEG documents       
+    - P2P security paper: "Asymptotically Efficient Approaches to 
Fault-Tolerance 
+      in Peer-to-Peer Networks"
+    - try to simulate a Tapestry network with Tapestry's simulation framework
+      - however, there's a bug in simbench's script that generates gnuplot 
commands 
+        (gnuplot throws an error and refuses to draw a graph)    
+
+2003-06-17 - 2003-08-1
     - write a PEG about implemented overlays
       which are implemented
     - important aspects: in addition to "standard" requirements, level of 
       development process and the license are important
-
-
-=============
-Past:
-=============
+    (- should be quite ready after benja's comments=
 
 2003-07-28
     - try finish available_overlays PEG
@@ -215,6 +227,7 @@
         http://www.cs.berkeley.edu/~zf/spamwatch/ (uses Tapestry as a P2P 
        routing platform)
     - explored Tapestry code base and read some Javadocs
+    
 
 2003-06-24 - 2003-06-27
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]