SBPROJECTS will be offline Wednesday between 7:30 and 8:30

SBForge with all its applications will be down for security updates during a time interval of about 10-20 minutes in the interval mentioned above.

Child pages
  • Message flow
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Normal message flow 

Normal message flow

  1. Identify requests: The client initiating an operation should start by sending an Identify request  to the broadcast Destination. The identify request asks all pillars and/or contributors who is capable and able to perform the operation to reply. The request includes the Destination whereto the pillars/contributors should send their responses.
  2. Identify responses: All pillars and/or contributors who support the operation and for whom the received Identify request is relevant, send responses back containing a Destination used by the client to send messages directly to the pillar/contributor. The responses can also include additional information about the pillars ability to respond. E.g. expected delivery time of a file.
  3. The client chooses which pillars to use for the operation
  4. Operation request: The client sends an Operation request message to each pillar/contributor chosen for the operation, requesting the specific operation to be performed. 
  5. Progress response: Each pillar can send Progress responses regarding the status of the operation process. The first progress message will typically be an 'Operation accepted' response'. It is not mandatory
  6. Final response: When a pillar has finished performing the requested operation, it sends an Final Response. The final response contains the final status of the operation, failure or success. It may also contain the result of the operation or information on where to get the results. 

The message flow above is described in a general form. Each type of message mentioned above is specific to the given operation type. The specific operations and their messages is listed on the Protocol messages page.

Other flows

  • Alarms: Alarms are sent directly to a Alarm Destination, where subscribers receive the alarm messages.
  • No labels