5 Answers, 1 is accepted
The pros of using the build-in Kendo UI transport is that you will receive the functionality out of the box. On the other hand if you define custom DataSource transport that uses AngularJS service/factory to handle data transfers you will have more control on the way client communicates with the server.
Which one you will prefer is a matter of preference and specific requirements.
Thank you. Are there any special recommendations/considerations you think we should take into account if we decide to build our own implementation. I'm thinking of settings or similar that could affect the performance, security etc of the Kendo UI components and such?
there is nothing Kendo UI specific that should affect the framework in this case. Feel free to pick the approach you find most suitable.
Do you have some samples of how to use the Kendo UI Datasource combined with a general AngularJS factory/services? Perhaps using a Kendo UI Grid which I guess is the most commonly used control for stuff like this although I guess it's not much difference in this regard to other Kendo UI controls.
Are there any obvious drawbacks to not use Kendo UI Datasource directly against the WebAPI? What about authentication?
Check this example. With it, the authentication part should be configured through the $http service.