Service - Contact Method (handlers): Difference between revisions

From Izara Wiki
Jump to navigation Jump to search
(Created page with "= Overview = One handler service per contact method, examples: * Email * SMS * Izara site notifier * 3rd party messenger services = Repository = ... (not yet configured) =...")
 
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 7: Line 7:
* 3rd party messenger services
* 3rd party messenger services


= Repository =
Some contact methods are not public and will be special case services that don't follow the projects standard transparency rules.


... (not yet configured)
= Handler Services =
 
* [[Service - Contact Method Email]]


= DynamoDB tables =
= DynamoDB tables =


* 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
* contactTag is a name set by the handler services, it is used in the User Contact Manager as the public name shown for the user's contact, it might be the actual contact detail, if the community want that type of contact method to be forced public, up to the handler


= 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 =


[[:Category:Working_documents - User Contact Manager|User Contact Manager]]
[[:Category:Working_documents - Contact Method (handlers)|Contact Method (handlers)]]


[[Category:Backend services| User Contact Manager]]
[[Category:Backend services| Contact Method (handlers)]]

Latest revision as of 09:36, 7 December 2020

Overview

One handler service per contact method, examples:

  • Email
  • 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.

Handler Services

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
  • contactTag is a name set by the handler services, it is used in the User Contact Manager as the public name shown for the user's contact, it might be the actual contact detail, if the community want that type of contact method to be forced public, up to the handler

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)

Working documents

Contact Method (handlers)