If you don’t know, SharePoint has two frameworks for development, the server-side object model and the client-side object model (CSOM). The server-side object model is used to run code on the SharePoint server, for example if you develop web parts, workflows, taxonomies, and so on.
The client-side object model is used to develop code that runs outside of the SharePoint server, for example in applications you have on your desktop, mobile device, in an external web page, and so on. Technically, CSOM interacts with SharePoint through web services, and I’ll tell you why it’s important to know this in just a moment.
I’ve previously mentioned that Microsoft intends to attack the mobile market with full force, and an important aspect of that goal is an extended CSOM. But which areas will receive some much needed love from Redmond?
To understand this, I’ve investigated two main types of documents. The first type is the documents that describe the new CSOM features directly. The second type are the web services documents that describe which areas get new web services with which client developers can interact directly without necessarily going through CSOM.
No comments:
Post a Comment