| Use Case ID: |
UC21.0 |
| Use Case Name: |
Cancel Reply to Peer Request |
| Created by: |
jwh |
| Date Created: |
Thu Jul 19 22:10:56 2001 |
| Last Updated by: |
jwh |
| Date Last Updated: |
Thu Jul 19 22:10:56 2001 |
Actor: User Application
Goal: Cancel a reply.
Description: Cancel a reply.
Preconditions:
- The engine must be started.
- The reply transmission is not complete.
- The reply to cancel must be valid.
Post conditions:
None.
Priority: High
Related Use Cases:
UC15.0 - Send Peer Request
UC16.0 - Send Peer Request Async
UC17.0 - Cancel Peer Request
UC20.0 - Reply to Peer Request
Notes and Issues:
None
Event Flow:
- The application asks the engine to cancel a reply sent to a peer.
- The engine cancels the reply transmission
- The engine removes the reply from its in progress list.
Alternate Flows:
UC21.1 Engine is not started
- The application asks the engine to cancel a reply message.
- The engine returns an error that the it has not been started.
UC21.2 Reply doesn't exist
- The application asks the engine to cancel a reply message.
- The engine returns an error that the reply doesn't exist.
UC21.3 Reply Already Set
- The application asks the engine to cancel a reply message.
- The engine returns an error that the engine has already sent the reply.
Sequence Diagrams:
Revision History
| Name |
Date |
Reason for Change |
Version |
| |
|
|
|
$Id: UC21.0.html,v 1.4 2001/07/26 01:58:10 james Exp $