LabsLab 04 · Intermediate · 20 min
API and server paging
Use a typed HttpClient, server-side paging, and explicit loading, empty, failure and cancellation states.
In this Blazor WebAssembly host: GitHub Pages has no server. The same typed HttpClient sends each request, and an in-browser HttpMessageHandler answers it with the same validation, latency, failure and cancellation rules. Run locally to send real HTTP requests.
1000
Load a page to send a request through the typed HttpClient.
Why it works
The API owns a deterministic read-only dataset. Only a bounded page crosses HTTP. Each request accepts a cancellation token and validates query bounds.
Try it yourself
Set latency, load and cancel; then simulate a failure. Search for an absent summary and inspect the empty state.