You can set serverside to false but continue to use ajaxsource. As mentioned in the documentation, this will cause a one-time ajax load of the data, after which all sorting and searching is done clientside
When you do the one-time ajax request it gets *all* of the rows from your server-side source. All the paging is done client-side afterwards. DataTables doesn't send any information to the server to tell it which subset/page of data to send back, since it's designed to get the entire dataset back if serverside == false.
Having client-side sorting and filtering for only the a single page at a time might be confusing to the user as they probably expect the sorting and filtering to apply to all the data, including the data from other pages.
Maybe allan has a solution for you but I wouldn't get your hopes up for that particular scenerio, sounds like it would be difficult to get around.
Replies
You can set serverside to false but continue to use ajaxsource. As mentioned in the documentation, this will cause a one-time ajax load of the data, after which all sorting and searching is done clientside
Having client-side sorting and filtering for only the a single page at a time might be confusing to the user as they probably expect the sorting and filtering to apply to all the data, including the data from other pages.
Maybe allan has a solution for you but I wouldn't get your hopes up for that particular scenerio, sounds like it would be difficult to get around.