The approach taken to implement paging support is greatly dependant upon the implementation of the underlying services/data sources providing the data.
If all the required information is available, it may be possible to use the 'Paging Table' control available with MVC WebMaker 3.1 to easily provide this functionality. For more details please see How do I use the Paging Table control?
If this option is not suitable, then you will need to determine how the data will be retrieved, and where it will be stored. For example, if your data source provides all the information in one go, you may want to cache it within MVC using a rule in the appropriate controller. You would then extract the relevant part from this to display on the screen. Alternatively, if your data source allows you to specify which 'page' of data to return then you would not need to cache any data, but would simply call the source each time to return the required data.
In either case you are likely to need to create some hidden fields on the page to store the current state of the screen (eg page number, or range displayed, etc.), and then add some buttons to provide next/previous page functionality. These buttons would call a Controller in which you would need to create the appropriate rules to either call the service again or take the relevant section of data from the cache.
If all the required information is available, it may be possible to use the 'Paging Table' control available with MVC WebMaker 3.1 to easily provide this functionality. For more details please see How do I use the Paging Table control?
If this option is not suitable, then you will need to determine how the data will be retrieved, and where it will be stored. For example, if your data source provides all the information in one go, you may want to cache it within MVC using a rule in the appropriate controller. You would then extract the relevant part from this to display on the screen. Alternatively, if your data source allows you to specify which 'page' of data to return then you would not need to cache any data, but would simply call the source each time to return the required data.
In either case you are likely to need to create some hidden fields on the page to store the current state of the screen (eg page number, or range displayed, etc.), and then add some buttons to provide next/previous page functionality. These buttons would call a Controller in which you would need to create the appropriate rules to either call the service again or take the relevant section of data from the cache.