Refactor data-shaping of paged list reads

Currently data shaping of paged list reads (HasPageInfo=true) is done by a restangular interceptor. This means that r=these reads have to be done with restangular, even though the collection is seldom required to be ‘restangularised’. Api classes can get simpler; the paged list read can be done by $http if the data shaping is done by an $http interceptor.

So an Api class on the client needs a read method ( via retangular, since this single object is usually available for editing) and a pagedlist via $http. Saving does not require the Api, becuase once the object is restangularised, it can save itself.

In an analogous way on the server, reads are done through the DataLayer DSxxx class for single objects (becuase these often use a stored proc to return a complex structured object) and the paged list. However, updates can be handled by entity fraamework (using the dynamic binder).

Comments (1)