If you have a table with a small amount of records you can load all the records into datatables and it will paginate everything for you.
If you have a large amount of records you should consider server side processing. This way the user is not refreshing the whole page but only the data for the table. Once you implement server side processing, the pagination will be controlled by datatables sending the iDisplayStart & iDisplayLength to the server which will alter the query for the correct data.
You can see the available example server side scripts here:
http://datatables.net/development/server-side/
This is also helpful to see what will be sent to the server and what the expected response is from the server:
Replies
If you have a large amount of records you should consider server side processing. This way the user is not refreshing the whole page but only the data for the table. Once you implement server side processing, the pagination will be controlled by datatables sending the iDisplayStart & iDisplayLength to the server which will alter the query for the correct data.
You can see the available example server side scripts here:
http://datatables.net/development/server-side/
This is also helpful to see what will be sent to the server and what the expected response is from the server:
http://datatables.net/usage/server-side
Rather is it possible on each page turn to generate a unique page url
Can I modify the URL based on the server response and what data from the server
Can I base the page id on?