Update docs for order of listeners #1805 (#1834)
This commit is contained in:
parent
638322d905
commit
9987893963
|
@ -132,6 +132,17 @@ For example:
|
||||||
async def close_db(app, loop):
|
async def close_db(app, loop):
|
||||||
await app.db.close()
|
await app.db.close()
|
||||||
|
|
||||||
|
Note:
|
||||||
|
|
||||||
|
The listeners are deconstructed in the reverse order of being constructed.
|
||||||
|
|
||||||
|
For example:
|
||||||
|
|
||||||
|
If the first listener in before_server_start handler setups a database connection,
|
||||||
|
ones registered after it can rely on that connection being alive both when they are started
|
||||||
|
and stopped, because stopping is done in reverse order, and the database connection is
|
||||||
|
torn down last.
|
||||||
|
|
||||||
It's also possible to register a listener using the `register_listener` method.
|
It's also possible to register a listener using the `register_listener` method.
|
||||||
This may be useful if you define your listeners in another module besides
|
This may be useful if you define your listeners in another module besides
|
||||||
the one you instantiate your app in.
|
the one you instantiate your app in.
|
||||||
|
|
Loading…
Reference in New Issue
Block a user