|
I am writing a Silverlight control which will display the data from SharePoint list for use in SharePoint 2010 site. I am considering wheather to use Client Object Model or SharePoint web services to achieve this task ? Are there any criteria or performance considerations in deciding which to use when ? UpdateThere has been a post on this topic by author of SPServces. Including the link below |
||||
|
|
|
If you can you should use the Client Object Model (CSOM) - it does not support that many features as the web services but are superior in a number of ways such as:
So, for performance you will likely suceed better using CSOM |
|||
|
|
|
You actually calling a web service when you use client object model according to this link. Of course use web service is more direct but i dont really care about performance penalty by using Client Object Model. The more concern is productivity improvement by using client object model. But if you more comfortable using web service, you can use it. |
|||
|
|
|
Client Object Model was designed to work mainly with list data, so the API is somehow limitted. Working with web services does not always mean parsing XML data, you can use REST API (ListData.svc) that will return JSON output. Some webservices allow to switch between SOAP and JSON response format. So, my advice would be use Client Object Model when suitable (lists, security), and in other scenarios call SharePoint web services. |
|||
|
|
|
I think using the Client-Object Model is the suitable option because as it's meant to be used with tools like Silverlight, .NET, etc. Also it provides more benefits. |
|||||
|
|
This MSDN article should also be listed when answering this question: |
|||
|
|
