ADO.NET Data Services 1.5: server driven paging.
We continue to consider new possibilities of ADO.NET Data Services 1.5 and today we will look possibility of compulsory breakdown of data into pages.
Possibility of breakdown of data on pages already was present at first version of Astoria. For these purposes it was possible to construct query by means of Take/Skip operators. Changing values of these parametres it was possible to get paginal access to data from the client. Nevertheless, at the access to a collection without parametres service returned completely all collection. The described behaviour seems quite logical, but it not always is desirable. For example, if in a collection the considerable quantity of objects the acceess to such collection will by all means entail the raised loading on a server contains. Therefore in version 1.5 the decision on addition of possibility of compulsory breakdown on pages was accepted.
To enable of the described possibility it is necessary to define additional behaviour in configuration of service. In particular SetEntitySetPageSize method which allows to define the size of page for each collection is necessary for us.
public class WebDataService : DataService<NorthwindEntities>
public static void InitializeService(DataServiceConfiguration config)
config.DataServiceBehavior.MaxProtocolVersion = DataServiceProtocolVersion.V2;
In case of described above service, at the access to Categories collection data will be broken into pages on five objects.
Apparently, for the access to the following page it is necessary to use a $skiptoken keyword. In this case URI format will look as follows:
The given functionality also is supported and in a client proxy. At the usual access to a collection the specified number of objects will be given out the client only. For the access to other pages it is necessary to use Skip() method.
var client = new NorthwindEntities(new Uri(@"..."));
var q = from c in client.Categories.Skip(2)
foreach (var item in q)