1 files changed, 29 insertions, 17 deletions

diff --git a/ISSUES b/ISSUES
index f68ad51..774edb6 100644
--- a/ISSUES
+++ b/ISSUES
@@ -347,17 +347,39 @@ public interface GnunetMessageBody extends MessageUnion { }
 
 ========================================================================================
 
-* client_api.c
+* are we in a hurry? when should gnunet-java be usable to students?
+ * 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)
+
+* 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?
+* once a MessageMap.txt has been generated for a new extension, how do we tell gnunet-java that/where it
+  exists?
+* what about allocation of message IDs for extesions / what about clashes?
+
+* 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
 
 * ...NOTIFY_PRE_CONNECT.. message type not used
 
-* what about allocation of message IDs for extesions / what about clashes?
 
 core:
 * we seem to get all incoming messages if the handlers array is empty (even if we don't request anything)
 * being notified about outbound messages does not seem to work at all
+ * 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?
+ * 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?
+
+* are there really any ambiguities when receiving messages with a runabout?
+
 
 
 * how does the Hash ascii-encoding work?
@@ -388,6 +410,8 @@ int[] foo;
 * server:
  * what is a MessageStreamTokenizer and why does it belong to the server?
   * my guess: for fragmented messages inside other messages?
+  * GNUNET_SERVER_connect_socket: what is it for?
+  * how to disable corking in java? is corking the same as TCP_NODELAY?
 
 
 * discuss: the size parameter in the various notifyTransmitReady methods
@@ -395,22 +419,10 @@ int[] foo;
  * proposal: keep for c api compatibility, introduce additional version that
    gets a message object directly, and calls a continuation to notify about success/failure
 
-* core:
- * 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?
- * 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?
 
 
-* GNUNET_SERVER_connect_socket: what is it for?
-* how to disable corking in java? is corking the same as TCP_NODELAY?
-
+* server:
+ * what is client_keep?
+ * when handling signals through the pipe, how is the service / server notified?
 
-* why is installing gnunet so compilicated?
- * e.g. stuff like "base of XYZ installation" in ./configure is very confusing
- * many dependencies with out-of-date packages on common distros