Freya GUI 库

Granian HTTP server

• 拥有单一、正确的 HTTP 实现，支持版本 1、2（最终是 3）
• 为多个平台提供单一包
• 避免 unix 系统上常见的 Gunicorn + uvicorn + http-tools 依赖组合
• 与现有替代方案相比，提供稳定的性能

Pavex DevLog #6: 设计安全且符合人体工程学的中间件

• 为什么中间件支持是生产就绪的关键要求
• 为 Rust Web 框架设计中间件系统的挑战
• Pavex的中间件设计
• 我们当前实施的局限性

use pavex::{middleware::Next, response::Response};
use std::future::IntoFuture;
use tokio::time::{timeout, error::Elapsed};

pub async fn timeout_middleware<C>(
// A handle on the rest of the processing pipeline for the incoming
// request. 
//
// Middlewares can choose to short-circuit the execution (i.e. 
// return an error and abort the processing) or perform some 
// computation and then delegate to `next` by awaiting it.
//
// All middlewares in Pavex *must* take `Next<_>` as an input.
    next: Next<C>,
// Middlewares can take advantage of dependency injection! 
// You just list what inputs you need and the framework will provide them
// (if possible, or return a nice error at *compile-time* if not).
//
// `TimeoutConfig` could be defined at start-up time, sharing the same 
// value for all routes, or it could be customised at runtime on a 
// per-request basis (e.g. to provide a configurable quality of service
// depending on the pricing plan of the client issueing the request).
// `timeout_middleware` doesn't care how or when `TimeoutConfig`
// gets computed. 
// Happy decoupling!
    config: TimeoutConfig
) -> Result<Response, Elapsed>
where
    C: IntoFuture<Output = Response>
{
    timeout(config.request_timeout, next.into_future()).await
}

• Rustcc论坛: 支持rss
• 微信公众号：Rust语言中文社区