Service - Contact Method (handlers): Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
* Each method will manage its own tables according to it's needs | * Each method will manage its own tables according to it's needs | ||
= Notes = | |||
* If method handler disables a contact, keep a record here as disabled, send a message to [[Service - User Contact Manager|User Contact Manager]] service to disable its entry | |||
= Ideas = | = Ideas = | ||
* Adding/changing contact method details will be managed within the handler services, some of this code can be standardized | |||
* Each handler service will send a message to the [[Service - User Contact Manager|User Contact Manager]] service on any pertinent changes (eg change of display tag, disabling a contact option) | |||
= Working documents = | = Working documents = | ||
Revision as of 11:18, 8 November 2020
Overview
One handler service per contact method, examples:
- SMS
- Izara site notifier
- 3rd party messenger services
Some contact methods are not public and will be special case services that don't follow the projects standard transparency rules.
Repository
... (not yet configured)
DynamoDB tables
- Each method will manage its own tables according to it's needs
Notes
- If method handler disables a contact, keep a record here as disabled, send a message to User Contact Manager service to disable its entry
Ideas
- Adding/changing contact method details will be managed within the handler services, some of this code can be standardized
- Each handler service will send a message to the User Contact Manager service on any pertinent changes (eg change of display tag, disabling a contact option)