Changes between Version 5 and Version 6 of TrickleMessages

Timestamp:

Sep 14, 2011, 1:10:18 PM (13 years ago)

Author:

davea

Comment:

--

TrickleMessages

@@ -2 +2 @@
 
 '''Trickle messages''' let applications communicate with the server during the execution of a workunit.
+Messages are XML documents, and they may go from client to server or vice-versa.
+Trickle messages are asynchronous, ordered, and reliable.
+Since they are conveyed in scheduler RPC messages, they may not be delivered immediately after being generated.
 
-Messages are XML documents, and they may go from client to server or vice-versa.
-
-Trickle messages are asynchronous, ordered, and reliable. Since they are conveyed in scheduler RPC messages, they may not be delivered immediately after being generated.
+See [TrickleApi the APIs for sending and handling trickle messages].
 
 == Trickle-up messages ==
+
 '''Trickle-up''' messages go from application to server.
 They are handled by '''trickle handler daemons''' running on the server.
@@ -14 +16 @@
 (This is used, typically, to distinguish different applications.) Example uses:
  * The application sends a trickle-up message containing its current runtime,
-   so that users can be granted incremental credit (rather than waiting until the end of the work unit).
+   so that users can be granted credit incrementally (rather than waiting until the end of the work unit).
+   BOINC supplies [TrickleCredit a trickle handler for this purpose].
  * The application sends a trickle-up message containing a summary of the computational state,
    so that server logic can decide if the computation should be aborted.