Changes between Version 12 and Version 13 of TracDev/Proposals/EmailValidation
- Timestamp:
- Dec 9, 2010, 12:13:00 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracDev/Proposals/EmailValidation
v12 v13 63 63 - It will provide a default implementation for that, namely !DefaultEmailAddressValidator, which is also the default validator used if none was configured. 64 64 - There exists only one active implementation of that extension point interface in the system, which will be configured via TracIni [notification], e.g. email.validator = !DefaultEmailAddressValidator 65 - The data model must be extended so that the validator can both register and track validation progress and state for given email addresses, it will do so by storing the hashes of these addresses only65 - The data model must be extended so that the validator can both register and track validation progress and state for given email addresses, it will do so by storing both the e-mail address and the associated validation hashes along with a state and a timestamp 66 66 - Clients of the TracNotificationAPI will then query the api for an instance of the validator, e.g. get_validator 67 67 - Clients of the validator will then be able to register new email addresses for validation. If an email address was validated before, the validator can query its data model for the hash of that email address and look up its state, they will also be able to unregister email addresses no longer in use by the system and they are also able to forcedly invalidate existing email addresses.