PEP #: 25
TITLE: Add a simple display consumer to test indications
Version : 1.2
Authors: Yi Zhou
State: Accepted
Approvals Required: Architecture Team
Type: Design
Created: 5 February 2003
Version History:
Version | Date | Authors | Reason |
1.0 | 5 February 2003 | Yi Zhou | Initial proposal | 1.1 | 13 February 2003 | Yi Zhou | Change to write indications to a file  | 1.2 | 28 March 2003 | Yi Zhou | Updated Status  |
Abstract: This PEP proposes to add a new simple display consumer which writes received indications to a file or prints out received indications on the screen. This will give pegasus developers a way to create automatic tests to test indication process, indication provider and so on.
Problem:
Pegasus currently does not have a mechanism to create automatic testing of indication process, indication delivering, and indication providers. The existing RT_IndicationConsumer only prints IndicationID, IndicationTime, and MethodName properties on the screen.
Solution:
This PEP proposes to add a new simple display consumer which writes all the properties of any indications it receives to file indicationLog. The indicationLog file is located in a directory which is configuring using the enviroinment variable PEGASUS_DISPLAYCONSUMER_DIR and default to PEGASUS_HOME. If the PEGASUS_DISPLAYCONSUMER_DIR is set to "console", the output will be written to stdout. Accompanying new test cases will also be added. This proposal will result in creation of the following directories and files:
Schedule:
Action | Planned | Actual | Comment |
PEP Submitted | 5 February 2003 | 5 February 2003 | |
PEP Reviewed | 14 February 2003 | 14 February 2003 | |
PEP Approved | 21 February 2003 | 21 March 2003 | |
Code Committed | 28 February 2003 | 28 March 2003 |