This is certainly not anything which is defined by MVC:
Absolute rubbish! The View contains variables which identify the limit, offset and sort order required by the user. These pass *THROUGH* the Model to the DAO where they are added to the relevant sql SELECT statement.
The VIEW does *NOT* decide which records to display, or in what order. It simply displays *ALL* the records it is given and in the order in which they are given.
This is called pagination and is automatically built into each of my Transaction Patterns, so absolutely *NO* extra code is required. EVER.
I have the same functionality built into my framework, so it is available within every relevant screen automatically without the need for any extra code.
It *IS* different on the web. If the user changes any of the variables which affect limit, offset or order then the whole page is refreshed, which means that the DAO completely rebuilds its data according to the new variables, and the View displays this new data. The View does not manipulate the data in any way, it simply displays it.
It is *ONLY* the DAO which processes the limit, offset and order variables - they merely pass through the Controller and Model on their way to the DAO. The View must include some method of allowing the user the change the limit, offset and order variables, but it does *NOT* process them