Use Case: Keeping Configuration Up-to-date

Summary

• Scope: libelektra-kdb
• Level: Developer Goal
• Actors: Application, Elektra
• Brief: Application wants up-to-date configuration data

Scenarios

• Precondition: -
• Main success scenario: Notifications
  • Application requests asynchronous callbacks via the notification system
  • Application loads configuration
  • Every time the configuration changes, Elektra sends a notification to Application
  • When receiving a notification, Application may need to load the configuration again
• Alternative scenario: Polling
  • Application loads configuration repeatedly in regular intervals
• Error scenario: -
• Postcondition: -
• Non-functional Constraints:
  • Notifications SHOULD use standard communication systems
  • there SHOULD NOT be a rate limit of notifications