alux-http-salvo 0.1.0

Salvo interpretation of ALUX typed HTTP programs
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

# alux-http-salvo

`alux-http-salvo` interprets an [`alux-http`](https://docs.rs/alux-http) program as executable
[Salvo](https://docs.rs/salvo) routes.

```rust ignore
use alux_http::HttpProgramExt;
use alux_http_salvo::SalvoHandlerImpl;

let api = SalvoHandlerImpl::new(App::new());
let router = api.compile_http(api.status_api::<App>()).into_salvo();

salvo::Server::new(salvo::conn::TcpListener::new("0.0.0.0:3000").bind().await).serve(router).await;
```

A Salvo handler writes into the response it receives rather than returning one, so every output kind
here produces a `salvo::Response` for the endpoint to install. Salvo represents path captures as a
map, even when the path has only one parameter. This interpreter extracts that single value directly,
so it agrees with the path semantics of the other routers.

## Closing

Salvo owns its accept loop but accepts through a `TcpAcceptor`, so this crate binds the listener and hands it over. Closing therefore goes through `ServerHandle::stop_graceful`, which stops accepting and then waits for connections already accepted to close.

That wait takes a timeout, and it matters: Salvo drops the acceptor only once the wait is over, so `stop_graceful(None)` lets one client holding a connection open hold the address with it. This crate passes 5 seconds, which is what keeps `close` bounded and its address released.