pub struct Limits {
pub max_payload_bytes: u64,
pub max_embedded_bytes: u64,
pub idempotency_key_ttl_seconds: Option<u32>,
pub max_publish_per_minute: Option<u64>,
}Expand description
Resource limits declared by the registry.
The capabilities document is OPEN at the top level, but limits is a
CLOSED sub-object (additionalProperties: false): new limit keys are
added by a spec version bump, not by registries inventing fields, so
deny_unknown_fields rejects an unknown key (RFC-ACDP-0007 §3.3.1,
conformance fixture schema-010).
Fields§
§max_payload_bytes: u64Maximum total publish request size in bytes.
max_embedded_bytes: u64Maximum size of any single embedded data reference in bytes (≤ 65536).
idempotency_key_ttl_seconds: Option<u32>How long idempotency-key mappings are retained, in seconds.
MUST be present when supports_idempotency_key is true.
Optional and absent-or-integer in the schema — not nullable.
de_present rejects an explicit "idempotency_key_ttl_seconds": null.
max_publish_per_minute: Option<u64>(0.3.0) OPTIONAL nominal per-agent publish ceiling, in
publishes per minute (integer ≥ 1). Advisory: producers SHOULD
use it to pace publishes; its presence does NOT change the
RFC-ACDP-0008 §4.3 requirements (rate limiting stays REQUIRED,
Retry-After stays mandatory on 429). RFC-ACDP-0007 §3.2,
fixture caps-007.