http-cache

HTTP response caching is implemented by wrapping your existing API client with a decorator that parses Cache-Control directives and handles ETag/Last-Modified conditional requests. This approach minimizes network calls and provides offline fallback support without changing call sites.

Stale-while-revalidate is a caching pattern that serves stale cached data immediately while fetching fresh data in the background. It improves API responsiveness by reducing wait times and supports offline UX when network connectivity is unavailable.

Offline support is added by wrapping your Swift API client with a caching decorator that uses disk and memory storage with LRU eviction. This intercepts network calls and serves cached responses when the network is unreachable, requiring no server modifications.

Per-endpoint cache policies are fully supported, allowing different caching behaviors for each API route. You configure cache-first, default, or custom policies per endpoint to satisfy production-grade requirements for bandwidth reduction and faster responses.

Handling 304 Not Modified responses is managed automatically through ETag and Last-Modified conditional requests. The cache layer validates cached entries against the server, preserving stored response data when validation succeeds and reducing payload transfers.

Avoid the decorator caching pattern if your application makes minimal API calls or has no offline requirements, as the disk and memory overhead provides little benefit. It is best suited for API-heavy apps needing reduced bandwidth and robust offline fallback.