Changes between Version 2 and Version 3 of TrickleImpl


Ignore:
Timestamp:
12/03/10 02:38:20 (7 years ago)
Author:
cries
Comment:

Changes of the databases tables names for Trickle-Messages.

Legend:

Unmodified
Added
Removed
Modified
  • TrickleImpl

    v2 v3  
    55When the core client sends an RPC to a server, it scans the project directory for these trickle-up files includes them in the request, and appends '.sent' to their filenames. On successful RPC completion it deletes trickle-up files that were sent earlier.
    66
    7 On the server, messages are stored in database tables 'trickle_up' and 'trickle_down'. The scheduling server extracts trickle messages from the request message and inserts them in the trickle_up table. If the 'trickle_down' flag in the configuration is set, it scans the database for trickle-down messages for this host and includes them in the reply message, setting the 'handled' flag in the DB record.
     7On the server, messages are stored in database tables 'msg_from_host' and 'msg_to_host'. The scheduling server extracts trickle messages from the request message and inserts them in the msg_from_host table. If the 'trickle_down' flag in the configuration is set, it scans the database for trickle-down messages for this host and includes them in the reply message, setting the 'handled' flag in the DB record.
    88
    99The client parses trickle-down messages in the scheduler reply, creates files of the form trickle_down_createtime_id in the slot directory, and signals the app via shared memory that a message is available.