[GNUnet-SVN] r26915 - in gnunet-java: . doc

[gnunet]

Author: dold
Date: 2013-04-17 12:47:29 +0200 (Wed, 17 Apr 2013)
New Revision: 26915

Modified:
   gnunet-java/ISSUES
   gnunet-java/build.gradle
   gnunet-java/doc/gnunet-java-tutorial.tex
Log:
issues, typo


Modified: gnunet-java/ISSUES
===================================================================
--- gnunet-java/ISSUES  2013-04-17 10:47:02 UTC (rev 26914)
+++ gnunet-java/ISSUES  2013-04-17 10:47:29 UTC (rev 26915)
@@ -1,3 +1,19 @@
+* i've seen multihashmap32, is it for consensus/set? ;)
+
+* discuss set service
+ * discuss how to split service into union/intersection
+ * acknowledgement similar to (but simpler than) mesh
+  * other solution would be to use one client per request, not per set
+  * but, this demonstrates the features of GNUNET_MQ ;)
+* discuss GNUNET_MQ
+ * set_api.c is quite concise
+ * message allocation
+ * request tracking
+ * handling of timeouts
+ * handling of incoming messages
+
+* discuss gnunet-java build system
+
 * error-reporting in construct is really bad
  * add information to exception while bubbling up the parser tree
   * only expensive on error

Modified: gnunet-java/build.gradle
===================================================================
--- gnunet-java/build.gradle    2013-04-17 10:47:02 UTC (rev 26914)
+++ gnunet-java/build.gradle    2013-04-17 10:47:29 UTC (rev 26915)
@@ -39,9 +39,13 @@
   }
 }
 
+task install (dependsOn: 'build', type: Copy) {
+
+}
+
+
 compileJava.options.debugOptions.debugLevel = "source,lines,vars"
 
-
 project.ext.instrumentDir = "$buildDir/classes_instrumented"
 project.ext.coberturaDir = "$projectDir/cobertura"
 project.ext.coverageData = "$projectDir/coverage.data"

Modified: gnunet-java/doc/gnunet-java-tutorial.tex
===================================================================
--- gnunet-java/doc/gnunet-java-tutorial.tex    2013-04-17 10:47:02 UTC (rev 
26914)
+++ gnunet-java/doc/gnunet-java-tutorial.tex    2013-04-17 10:47:29 UTC (rev 
26915)
@@ -257,7 +257,7 @@
 message consists of a header (with the message size and the message
 type) and a body.
 
-You can define a new type of nessage in GNUnet-Java by annotating a
+You can define a new type of message in GNUnet-Java by annotating a
 class with information on how to represent its members in binary format.
 
 Additionaly, you have to register your new message type with
@@ -445,7 +445,7 @@
 \end{lstlisting}
 
 Always remember to call {\tt getSender().receiveDone()}, as the server does 
not receive further messages
-until {\tt receiveDone is called}, in order to support flow control.
+until {\tt receiveDone} is called, in order to support flow control.
 The object returned by {\tt getSender()} has a {\tt notifyTransmitReady} 
method, which can be used
 to send messages to clients in a similar fashion to writing to CORE.