Mercurial > prosody-modules
view mod_graceful_shutdown/README.markdown @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Tue, 21 Mar 2023 21:57:18 +0100 |
| parents | 999e7cb7f6d9 |
| children |
line wrap: on
line source
::: {.alert .alert-warning} This module is an experiment about a more graceful shutdown process. Graceful shutdown has now been implemented in Prosody trunk and will be part 0.12. See [issue #1225](https://issues.prosody.im/1225) for details. ::: Why === When shutting down, a number of sessions, connections and other things are teared down. Due to all these things happening very quickly, sometimes e.g. client unavailable notifications don't make it to all remote contacts because the server-to-server connections are teared down just after. How === This module works by breaking the shutdown process into separate steps with a brief pause between them. It goes something like this 1. Stop accepting new client connections. 2. Close all client connections. 3. Fire event for everything else. 4. Tell `net.server` to quit the main loop. 5. ??? 6. Still here? Kill itself.