File: serverSide.xml

package info (click to toggle)
datatables.js 1.10.13%2Bdfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 6,232 kB
  • ctags: 1,329
  • sloc: xml: 10,249; php: 4,387; sh: 492; makefile: 21
file content (30 lines) | stat: -rw-r--r-- 1,628 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
<?xml version="1.0" encoding="UTF-8" ?>
<dt-option group="feature">
	<name>serverSide</name>
	<summary>Feature control DataTables' server-side processing mode.</summary>
	<since>1.10</since>

	<type type="boolean" />
	<default>false</default>

	<description>
		DataTables has two fundamental modes of operation:

		* Client-side processing - where filtering, paging and sorting calculations are all performed in the web-browser.

		* Server-side processing - where filtering, paging and sorting calculations are all performed by a server.

		By default DataTables operates in client-side processing mode, but can be switched to server-side processing mode using this option. Server-side processing is useful when working with large data sets (typically >50'000 records) as it means a database engine can be used to perform the sorting etc calculations - operations that modern database engines are highly optimised for, allowing use of DataTables with massive data sets (millions of rows).

		When operating in server-side processing mode, DataTables will send parameters to the server indicating what data it needs (what page, what filters are applied etc), and also expects certain parameters back in order that it has all the information required to display the table. The client-server communication protocol DataTables uses is [detailed in the DataTables documentation](//datatables.net/manual/server-side).
	</description>

	<example title="Enable server-side processing"><![CDATA[
$('#example').dataTable( {
  "serverSide": true,
  "ajax": "xhr.php"
} );
]]></example>

	<related type="option">ajax</related>
</dt-option>