[GNUnet-SVN] r20964 - gnunet-java

[gnunet]

Author: grothoff
Date: 2012-04-12 15:02:48 +0200 (Thu, 12 Apr 2012)
New Revision: 20964

Modified:
   gnunet-java/ISSUES
Log:
-remarks

Modified: gnunet-java/ISSUES
===================================================================
--- gnunet-java/ISSUES  2012-04-12 12:55:56 UTC (rev 20963)
+++ gnunet-java/ISSUES  2012-04-12 13:02:48 UTC (rev 20964)
@@ -235,6 +235,7 @@
  ====================================================
 
  * how much stuff related to gnunet (and not just gnunet-java) should the 
tutorial cover?
+   
 
  * regarding IzPack:
   * are there really any advantages over just shipping a zip-file?
@@ -321,7 +322,9 @@
 
 * DHT:
  * gnunet-service-dht -h produces segfault
+   -> not anymore
  * block type "any" does not work on request (gnunet-dht-get always changes 
any to test)
+   -> yes, any indicates default here ;-)
  * why is there no ack from the dht that a put request has been received?
  * how unique is the UID? globally? per connection?
   * by looking at the sources: (client,uid) identifies a request unambiguously
@@ -354,11 +357,11 @@
 
 
 
-* are we in a hurry? when should gnunet-java be usable to students?
+* are we in a hurry? when should gnunet-java be usable to students? --- 23.4.
  * according to the website the project begins very soon
 * currently my progress with the tutorial is not that far, as the java APIs 
are not
   yet completely implemented / stable.
-* needed: a place to host the javadocs (so the tutorial can link to it)
+* needed: a place to host the javadocs (so the tutorial can link to it)  -> 
address@hidden
 
 * what is the best way to configure the classpath for gnunet-java-ext?
  * a bash script that exports environment variables for e.g. the 
gnunet-java.jar?
@@ -369,21 +372,25 @@
 * core_api.c, notify_transmit_ready:
   * pr = GNUNET_CONTAINER_multihashmap_get (handle->peers, 
&target->hashPubKey);
   * the above line crashes when target==NULL, but comment indicates that NULL 
is valid for target
+   => bad comment, fixed
 
-* ...NOTIFY_PRE_CONNECT.. message type not used
+* ...NOTIFY_PRE_CONNECT.. message type not used => DCE
 
 
 core:
 * we seem to get all incoming messages if the handlers array is empty (even if 
we don't request anything)
+  => correct
 * being notified about outbound messages does not seem to work at all
+  => bug
  * comment in core_connect talks about timout, but there is no timeout 
parameter.
  * GNUNET_MESSAGE_TYPE_CORE_NOTIFY_STATUS_CHANGE not used
   * also GNUNET_CORE_OPTION_SEND_STATUS_CHANGE
  * inconsistency in structs with trailing ATS information 
(NotifyTrafficMessage vs ConnectNotifyMessage)
-  * why zero-termination *and* size field?
-  * what does zero-termination really mean? is it only one byte? a whole ats 
entry?
+  * why zero-termination *and* size field? => legacy, we want NO zero 
termination anymore => file Mantis reports
+  * what does zero-termination really mean? is it only one byte? a whole ats 
entry? (double-zero)
  * what happens when we can't connect to core / lose connection? in the c api 
implementation, this is never handeled?
-  * why is there even the init callback if init can't fail?
+   -> auto-retry
+  * why is there even the init callback if init can't fail? => get PID
 
 * are there really any ambiguities when receiving messages with a runabout?
 
@@ -391,14 +398,14 @@
 
 * how does the Hash ascii-encoding work?
 * => solved, ported C-code, encountered some problems because of the lack of 
unsigned in java
-  (had to use long instead of int in java code because of sign)
+  (had to use long instead of int in java code because of sign) => fun
 * first implementation got some characters wrong, had to use
   byte b = data[(int) rpos++];
   int s = b >= 0 ? b : (256 + b);
   to compensate for the signed-ness of byte
 * is the current implementation correct now? (it has the same output as 
peerinfo)
+  => most likely.  Compare with gnunet-rsa!
 
-
 @Fill
 UInt32Message[] foo;
 
@@ -413,7 +420,19 @@
 @Fill @UInt32
 int[] foo;
 
+YES, like this (ideally):
 
address@hidden @
+int foo_length;
+
address@hidden @ArrayLength(length="foo_length")
+int[] foo;
+
address@hidden @Fill
+int[] bar;
+
+
+
 * server:
  * what is a MessageStreamTokenizer and why does it belong to the server?
   * my guess: for fragmented messages inside other messages?