One of the mechanisms which was provided in WCF Data Services from the start was client side paging. In the new release of WCF Data Services, we also get server side paging and this will be addressed in this post.
WCF Data Services Client Side Paging
From the early days of WCF Data Services, we could achieve paging on the client side using the
$skip query parameters. For example, the following URI for a data service will bring the 11-20 courses which were requested:
The problem starts when you expose resources with a lot of items. Let's say that we have 10000 courses in our course library. The following URI will bring to the client all of them:
Running this request will decrease the amount of clients for the service since it will take ages for the query to return. So what can we do? Use server side paging instead.
WCF Data Services Server Side Paging
So how can we limit our returning result set to the client? We can use a new feature of WCF Data Services. In order to create a server side paging behavior, all we need to do is to configure the service to return some portion of data. We will use the new method
DataServiceConfiguration class which is called
SetEntitySetPageSize for each entity set or for all of them at once (using * ). The following code creates server side paging for all the entity sets exposed by the data service to return only 10 items at once:
public class SchoolDataService : DataService<SchoolEntities>
public static void InitializeService(DataServiceConfiguration config)
config.DataServiceBehavior.MaxProtocolVersion = DataServiceProtocolVersion.V2;
When I use the service now with a URI to retrieve all the courses, I will get only the first ten courses. Also, as you can see in the figure, we get a link at the bottom that leads us to the next ten results:
and the link itself is written as:
In the new release of WCF Data Services, we get a new paging feature which enables server side paging. Using this method or combining it with client side paging extends the capabilities of WCF Data Services. The use of the server side paging is very easy – just configure the service. In the post, I showed an example of how you can achieve that behavior.