pub struct Esp32S3<A = Global, const MAX_REQUEST_HANDLERS: usize = prns_core::::storage::impls::esp32s3::Esp32S3::{constant#0}>(/* private fields */)
where
A: Allocator;Expand description
The PSRAM-backed ESP32-S3 storage profile.
MAX_REQUEST_HANDLERS is independent from the upstream-application destination capacity:
applications commonly register several request paths on one destination. It defaults to the
historical two rows, while application recipes with more routes should supply their exact
registration count.
Implementations§
Source§impl<A, const MAX_REQUEST_HANDLERS: usize> Esp32S3<A, MAX_REQUEST_HANDLERS>where
A: Allocator,
impl<A, const MAX_REQUEST_HANDLERS: usize> Esp32S3<A, MAX_REQUEST_HANDLERS>where
A: Allocator,
pub const TRACKED_DESTINATIONS: usize = MAX_TRACKED_DESTINATIONS
Sourcepub const LINK_SESSIONS: usize = MAX_LINK_SESSIONS
pub const LINK_SESSIONS: usize = MAX_LINK_SESSIONS
Cheap retained sessions outnumber every configured auto-interface fleet member, leaving admission room without multiplying resource or channel workspaces.
Sourcepub const MAX_OUTGOING_RESOURCE_REACTION_FRAMES: usize
pub const MAX_OUTGOING_RESOURCE_REACTION_FRAMES: usize
The most frames one resource request can synchronously emit for this storage recipe.
A request names at most WINDOW_MAX existing parts, and a response can append one hashmap
update. Compact layouts cannot materialize a full 75-part resource, so deriving the bound
from their outgoing store avoids reserving unreachable transport backlog on every lane.