mirror of https://github.com/rwf2/Rocket.git
0bdb6b7bc7
Launch fairings are now fallible and take the place of attach fairings,
but they are only run, as the name implies, at launch time.
This is is a fundamental shift from eager execution of set-up routines,
including the now defunct attach fairings, to lazy execution,
precipitated by the transition to `async`. The previous functionality,
while simple, caused grave issues:
1. A instance of 'Rocket' with async attach fairings requires an async
runtime to be constructed.
2. The instance is accessible in non-async contexts.
3. The async attach fairings have no runtime in which to be run.
Here's an example:
```rust
let rocket = rocket::ignite()
.attach(AttachFairing::from(|rocket| async {
Ok(rocket.manage(load_from_network::<T>().await))
}));
let state = rocket.state::<T>();
```
This had no real meaning previously yet was accepted by running the
attach fairing future in an isolated runtime. In isolation, this causes
no issue, but when attach fairing futures share reactor state with other
futures in Rocket, panics ensue.
The new Rocket application lifecycle is this:
* Build - A Rocket instance is constructed. No fairings are run.
* Ignition - All launch fairings are run.
* Liftoff - If all launch fairings succeeded, the server is started.
New 'liftoff' fairings are run in this third phase.
|
||
|---|---|---|
| .. | ||
| 0-introduction.md | ||
| 1-quickstart.md | ||
| 2-getting-started.md | ||
| 3-overview.md | ||
| 4-requests.md | ||
| 5-responses.md | ||
| 6-state.md | ||
| 7-fairings.md | ||
| 8-testing.md | ||
| 9-configuration.md | ||
| 10-pastebin.md | ||
| 11-conclusion.md | ||
| index.md | ||