Confirmed users
1,022
edits
CloudServices/Notifications/Push: Difference between revisions
Jump to navigation
Jump to search
CloudServices/Notifications/Push (view source)
Revision as of 21:18, 18 October 2011
, 18 October 2011→Use Cases
No edit summary |
|||
| Line 33: | Line 33: | ||
== Use Cases == | == Use Cases == | ||
''Email Notice'' - | |||
A webapp provider wishes to communicate with their audience. The provider has a set of user tokens for their customers. They then send messages to token@mozillamessaging.com (domain tbd). Notifications parses the message, wraps the message in a useful wrapper, and then relays the message to the registered user address, thus providing the user the ability to quiet noisy providers, drop compromised addresses and otherwise manage their message delivery. | |||
''Event Alert'' - | ''Event Alert'' - | ||
| Line 41: | Line 44: | ||
A user no longer wishes to receive alerts for a given notification. The user | A user no longer wishes to receive alerts for a given notification. The user | ||
loads their admin and control panel and disables the queue. The user can either temporarily silence a given notification queue (in which case, notifications are still collected, but not immediately alerted to the user) or delete the queue (in which case, incoming notifications are rejected, existing notifications are removed, and the queue is no longer associated with the user.) | loads their admin and control panel and disables the queue. The user can either temporarily silence a given notification queue (in which case, notifications are still collected, but not immediately alerted to the user) or delete the queue (in which case, incoming notifications are rejected, existing notifications are removed, and the queue is no longer associated with the user.) | ||
== Operational Requirements == | == Operational Requirements == | ||