Expand description
§avx-http - AVL Platform HTTP Client/Server
Native HTTP library optimized for Brazilian infrastructure and AVL Platform services.
§Features
- High Performance: < 500µs request overhead, 100k+ req/s
- Brazilian Optimized: Regional routing, smart retries
- AVL Platform Native: Built-in auth, telemetry, AvilaDB integration
- Developer Friendly: Simple async/await API
§Quick Start
§Client
use avx_http::Client;
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let client = Client::builder()
.build()?;
let response = client
.get("https://api.avila.cloud/data")
.send()
.await?;
println!("Status: {}", response.status());
Ok(())
}§Server
use avx_http::{Server, Router, Response};
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let router = Router::new()
.get("/", || async { Response::text("Hello!") });
Server::bind("0.0.0.0:3000")
.router(router)
.run()
.await?;
Ok(())
}Re-exports§
pub use error::Error;pub use error::Result;pub use client::Client;pub use client::ClientBuilder;pub use client::Request;pub use client::Response as ClientResponse;pub use pool::ConnectionPool;pub use pool::PoolConfig;pub use pool::PoolStats;pub use streaming::StreamingBody;pub use streaming::ChunkedEncoder;pub use streaming::SseStream;pub use interceptors::Interceptors;pub use interceptors::RequestData;pub use interceptors::ResponseData;pub use interceptors::RequestInterceptor;pub use interceptors::ResponseInterceptor;pub use server::Server;pub use server::Router;pub use server::Response as ServerResponse;pub use middleware::Middleware;pub use middleware::Next;pub use middleware::Handler;pub use middleware::Logger;pub use middleware::Cors;pub use middleware::RateLimit;pub use middleware::Auth;
Modules§
- client
- HTTP Client implementation
- error
- Error types for avx-http
- interceptors
- Request and response interceptors
- middleware
- Middleware system for HTTP server
- pool
- Connection pooling for efficient TCP connection reuse
- server
- HTTP Server implementation
- streaming
- Streaming support for HTTP requests and responses
Structs§
- Header
Map - A set of HTTP headers
- Header
Value - Represents an HTTP header field value.
- Method
- The Request Method (VERB)
- Status
Code - An HTTP status code (
status-codein RFC 9110 et al.). - Uri
- The URI component of a request.
Constants§
- VERSION
- Library version