Actor: User Application

Goal: Handle an incoming request and return a response.

Description: Handle an incoming request and return a response.

Preconditions:

1. The engine is started.
2. A valid request has been received.

1. A response has been sent to the requestor.

Related Use Cases:

UC15.0 - Send Peer Request
UC16.0 - Send Peer Request Async
UC20.0 - Reply to Peer Request
UC25.0 - Build Peer Message

Notes and Issues:

None

Event Flow:

1. The engine receives a valid request.
2. The engine dispatches the request to the appropriate receiver (application or service).
3. The receiver is informed of the request.
4. The receiver processes the request successfully.
5. The receiver constructs a reply message (see UC25.0 - Build Peer Message)
6. The receiver sends a reply (see UC20.0 - Reply to Peer Request).
7. The receiver informs the engine that the request was processed.
8. The engine marks the request as processed.

UC27.1 Error during processing

1. The engine receives a valid request.
2. The engine dispatches the request to the appropriate receiver (application or service).
3. The receiver is informed of the request.
4. The receiver processes the request with a resulting error due to bad data.
5. The receiver constructs a reply message with the error (see UC25.0 - Build Peer Message)
6. The receiver sends an error reply (see UC20.0 - Reply to Peer Request).
7. The receiver informs the engine that the request was processed.
8. The engine marks the request as processed.

Sequence Diagrams:

Revision History

Name	Date	Reason for Change	Version