Bear Bibeault wrote:
Winston Liek wrote:1. Send all data(~2000 rows) during get operation then use pagination to display 100 rows per page
Why grab data that you are not going to display?
What I mean is I will return all the data when the page initially loads then use pagination... So that when the user clicks next page/desired page, it will not send request since the data is in the user's page already(just hiding it)
Send only 100 row then calculate pagination and send ajax request when user clicks on page numbers
Better. Again, why bother fetching data that's not going to be used?
Part of the requirement is that the user won't have any filtering functionality (such as input id to filter then click search) since almost all will be encoded once finished.
We need to display the table when the page is loaded. It's just a matter of how will we display all the results
In terms of efficiency and I need to fast load it.
When and if you discover a performance issue, it can be addressed. Until such a time, anything else is premature optimization.
how will the user save his encoded data on current page if he will navigate to the next/other page?
I don't know what you mean by a user "saving his data".
Since each row in the table has input type text fields and we will be using pagination. For example, the result have 10 page numbers. The user inputs on the first page then finished encoding on the first page. If he clicks 'Next' button and I used option 2, the encoded data on page 1 will be discarded and moved to page 2.