/ 
PAGI-0.002011

Changes for version 0.002011 - 2026-09-30

  • Specification
    • Transport backpressure callbacks are flow-control signals, not an audit log of buffer changes. Servers MAY evaluate watermarks after immediate, non-blocking write attempts, so a transient high-water crossing that leaves the buffer below the high mark need not fire a callback pair. Once backpressure is engaged, draining below the low mark MUST release waiting sends and invoke armed on_drain callbacks, whether the drain happens through immediate or deferred writes.
    • Remove the incorrect note that ASGI servers keep a connection alive after a post-completion exception; uvicorn closes it. The rule itself is unchanged: the server MAY close the connection.

Documentation

CONTRIBUTING.md
README.md
SECURITY.md
PAGI::Building
building frameworks and toolkits on PAGI
PAGI::Cookbook
worked, runnable recipes for the PAGI protocol
PAGI::EventLoops
how PAGI stays loop-agnostic, how not to block, and how a server binds to an event loop
PAGI::PSGI
coming to PAGI from PSGI
PAGI::Spec
The base PAGI specification: application interface and core concepts
PAGI::Spec::Extensions
The PAGI server extension mechanism
PAGI::Spec::Lifespan
The PAGI Lifespan protocol for startup and shutdown events
PAGI::Spec::Server
PAGI server and application-runner integration guidance
PAGI::Spec::Tls
The PAGI TLS extension for reporting connection security in scope
PAGI::Spec::Www
PAGI message formats for HTTP, WebSocket, and SSE
PAGI::Tutorial
Learn the PAGI protocol for async Perl web applications
PAGI::Upgrading
What changed between sub-spec versions, and what to do about it

Modules

PAGI
Perl Asynchronous Gateway Interface

Examples

Other files