DataTables Client-Side and Server-Side Processing: Pagination State at the AJAX Boundary

Processing Models and the AJAX Contract

DataTables 1.10 and later supports two distinct processing models: client-side mode, where the entire dataset is loaded into the browser for instant sorting and pagination, and server-side mode, where pagination, filtering, and ordering are delegated to a backend via AJAX. In server-side mode, DataTables depends on the endpoint to return a specific JSON object containing draw, recordsTotal, and recordsFiltered. The draw counter discards out-of-order asynchronous responses, while the record counts drive the pagination interface.

Interoperability Uncertainty

The unresolved decision concerns the interoperability boundary when client-side configuration options—such as column visibility, search panes, or custom search inputs—alter the effective dataset without being fully represented in the standard server-side request parameters. If the backend calculates recordsFiltered independently of these client-side transformations, the pagination controls may display a page count that does not match the rows actually rendered. Conversely, if the client adjusts counts locally, it risks conflicting with the authoritative server response.

Open Questions

Where should the boundary between DataTables' client-side state and the backend's server-side JSON contract be drawn to keep pagination consistent? Which client-side features must the backend endpoint account for when computing recordsTotal and recordsFiltered, and how should the draw sequence guard behave when multiple overlapping filter sources are active?