While the purpose of a Javascript driven table is the prevention of reloads and server performance hits with repeating calls of table content after filtering or sorting or changing the limits of items show, etc., by loading all data in the background, we need a cache idea to prevent a unique very large and slow server hit by calling a table of 2000 or more complex items. Since the way how such Javascript implementions work by "hiding the rest until it is required" makes a 100% call of ALL data even if just 10 or 50 of them are shown to a server hug. In such cases it would be great if we could work on a second level of scalable cache paging option to, let's say, change the difference between shown and called/cached items step by step. Like if we would have 2 pagers, one for the view and another next level for the "middle cached page" holding the viewable pages already loaded.
Example:
.
All changable of course. Thougths? Let's talk about it ;-)
Active
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.