Changes between Version 4 and Version 5 of TrickleMessages


Ignore:
Timestamp:
Sep 14, 2011, 12:26:31 PM (13 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TrickleMessages

    v4 v5  
    11= Trickle messages =
    22
    3 '''Trickle messages''' let applications communicate with the server during the execution of a workunit. They are intended for applications that have long workunits (multiple days).
     3'''Trickle messages''' let applications communicate with the server during the execution of a workunit.
    44
    55Messages are XML documents, and they may go from client to server or vice-versa.
    … …  
    88
    99== Trickle-up messages ==
    10 '''Trickle-up''' messages go from application to server. They are handled by '''trickle handler daemons''' running on the server. Each message is tagged with a 'variety' (a character string). Each daemon handles messages of a particular variety. (This is used, typically, to distinguish different applications.) Example uses:
    11  * The application sends a trickle-up message containing its current CPU usage, so that users can be granted incremental credit (rather than waiting until the end of the work unit).
    12  * 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.
     10'''Trickle-up''' messages go from application to server.
     11They are handled by '''trickle handler daemons''' running on the server.
     12Each message is tagged with a 'variety' (a character string).
     13Each daemon handles messages of a particular variety.
     14(This is used, typically, to distinguish different applications.) Example uses:
     15 * The application sends a trickle-up message containing its current runtime,
     16   so that users can be granted incremental credit (rather than waiting until the end of the work unit).
     17 * The application sends a trickle-up message containing a summary of the computational state,
     18   so that server logic can decide if the computation should be aborted.
    1319
    14 To create a trickle handler daemon, modify the program sched/trickle_handler.cpp, replacing the function handle_trickle() with your own function. Add an entry in your [ProjectConfigFile config.xml] to run this program as a daemon.
     20To create a trickle handler daemon, modify the program sched/trickle_handler.cpp,
     21replacing the function handle_trickle() with your own function.
     22Add an entry in your [ProjectConfigFile config.xml] to run this program as a daemon.
    1523
    1624== Trickle-down messages ==
    1725
    18 '''Trickle-down''' messages go from server to application. Each one is addressed to a particular host, and must include an element <result_name> identifying the result to which the message is addressed. If that result is still running on the host, it is delivered to it. Example uses:
     26'''Trickle-down''' messages go from server to application.
     27Each one is addressed to a particular host,
     28and must include an element <result_name> identifying the result to which the message is addressed.
     29If that result is still running on the host, it is delivered to it. Example uses:
    1930 * The server sends a message telling the application to abort.
    2031 * The server sends a message containing the user's current total credit.