Struct JmapServer 

pub struct JmapServer;

JMAP server.

Construct routes with Self::routes_with_auth to wire a real authentication backend. The bare Self::routes constructor returns a router that 401s every request and exists primarily for tests that only exercise the routing surface.

Implementations

impl JmapServer

pub fn routes_with_auth(auth: SharedAuth) -> Router

Build the JMAP HTTP routes with a real AuthBackend.

Every route is wrapped by the authentication middleware so handlers receive a guaranteed-present Principal in their extensions, and by the connection-tracking middleware that maintains rusmes_active_connections{protocol="jmap"} plus the TLS counter.

This mounts only the core JMAP API endpoints (session + method dispatch). For blob and EventSource routes, use Self::routes_with_auth_and_state.

pub fn routes_with_auth_and_state( auth: SharedAuth, blob_storage: BlobStorage, event_manager: EventSourceManager, ) -> Router

Build the full JMAP HTTP routes including blob storage and EventSource push.

In addition to the core JMAP routes from Self::routes_with_auth, this mounts the following endpoints behind the same require_auth middleware:

• POST /upload/:account_id — blob upload (RFC 8620 §6.2)
• GET /download/:account_id/:blob_id/:name — blob download (RFC 8620 §6.2)
• GET /eventsource — Server-Sent Events push channel (RFC 8620 §7.3)

All routes enforce authentication via require_auth before dispatching to their respective handlers.

pub fn routes() -> Router

Build the JMAP HTTP routes WITHOUT an auth backend.

Every request is rejected with 401. This exists so the public API remains call-compatible during the transition window — callers that previously relied on the unauthenticated dev path should migrate to Self::routes_with_auth.