Password sync plugin, and questions about plugin criticality

[Luke Howard]

>>Conversely, you can collapse them into one without separating
>>quality checking from pre-commit synchronization, as long as
>>the plugin can return some value which indicates whether the
>>password change should be aborted.
>
>I don't see how that meets the goal of having it done before or
>after the password gets written locally.  I mean, you're presumably
>only calling the function before or after the password gets
>written to the local database.  Some people empatically want it
>one way, some people emphatically want it the other way.

I was referring to collapsing quality checking and pre-commit
synchronization, not pre- and post-commit synchronization.


cheers,

-- Luke

--