I'm a bit unclear on web services and data providers.
I'm wondering why WCF and web service functionality exist if they require a data provider.
If I use a data provider does this not prevent postbacks? Would an insert on a RadScheduler with a provider for example cause a postback and then fire the providers insert method? If it doesn't stop postbacks then I can understand the need to use WCF or web services as a facade/proxy to prevent postbacks.
I'm wondering why WCF and web service functionality exist if they require a data provider.
If I use a data provider does this not prevent postbacks? Would an insert on a RadScheduler with a provider for example cause a postback and then fire the providers insert method? If it doesn't stop postbacks then I can understand the need to use WCF or web services as a facade/proxy to prevent postbacks.
1 Answer, 1 is accepted
0
Hello Brett,
Thank you for the good question.
Providers by themselves can't eliminate postbacks. They're are just a thin abstraction over the data storage that is currently used. Data still needs to get to them in some manner. In a normal scenario this would be a postback that carries information about the performed operation.
In a Web Service scenario scenario all operations are routed to the dedicated service. In this case providers are a requirement, as normal data source controls can't be used without a page to host them.
Strictly speaking you can implement the web service methods without a provider, but you'll have to implement all the additional logic handled by the WebServiceAppointmentController. Having a common provider interface allows us to encapsulate this logic.
I hope this sheds some light into this matter. Let us know if you have any further questions.
Regards,
Tsvetomir Tsonev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Thank you for the good question.
Providers by themselves can't eliminate postbacks. They're are just a thin abstraction over the data storage that is currently used. Data still needs to get to them in some manner. In a normal scenario this would be a postback that carries information about the performed operation.
In a Web Service scenario scenario all operations are routed to the dedicated service. In this case providers are a requirement, as normal data source controls can't be used without a page to host them.
Strictly speaking you can implement the web service methods without a provider, but you'll have to implement all the additional logic handled by the WebServiceAppointmentController. Having a common provider interface allows us to encapsulate this logic.
I hope this sheds some light into this matter. Let us know if you have any further questions.
Regards,
Tsvetomir Tsonev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.