Architecture Share Point 2010

The client object model has three variants:

JavaScript Client Object Model This version is implemented in %SPRoot% Template Layouts SP. js. A lot of the new functionality in the SharePoint 2010 user interface is implemented using the JavaScript Object Model,and you saw some examples of this in Chapter 3’s discussion of the ribbon. The JavaScript Object Model is useful for enhancing the user experience without requiring additional plug-ins.

Silverlight Client Object Model This version was designed for use by Silverlight client applications and is implemented in%SPRoot%Template Layouts ClientBin Microsoft. SharePoint. Client. Silverlight. dll and Microsoft. SharePoint. Client . Silverlight. Runtime. dll. The Silverlight object model is useful when you’re developing a more visually appealing and interactive user experience. While JavaScript is useful for improving the interactivity of the user interface by minimizing server-side post backs and page redrawing, at the end of the day, the visual presentation is still constrained by the limitations of HTML. Silverlight has no such limitations, and when you’re using the Silverlight Object Model, creating user interface components that reference SharePoint data is relatively straightforward.

Managed Client Object Model This version has been designed for use by .NET-managed applications and is implemented in %SPRoot%ISAPIMicrosoft .SharePoint.Client.dll and Microsoft.SharePoint.Client.Runtime.dll. As Silverlight and JavaScript are great tools for developing a rich webbased user interface. However, the services available on the SharePoint platform are not only useful to web clients, but they have myriad uses in rich-client applications as well. For example, using a SharePoint document library as the data store for a purchasing application would allow users to store created purchase orders in a web-based system that could be used as an extranet tool by suppliers. Although each of these variants has a slightly different implementation, in terms of the capabilities exposed and the way that the object model works, they are all practically identical. Each Client Object Model variant exposes a number of client-side representations of server-side objects. Communication from the client-side object to the server-side counterpart is accomplished via a new Windows Communication Foundation (WCF) service called Client.svc, as the following illustration shows:

Managed Client Object Model

Effectively, Client.svc acts as a proxy for the actions performed on the client. It performs the appropriate actions using the Server Object Model and returns the results to the client using the lightweight JavaScript Object Notation (JSON) data exchange format.

From an implementation perspective, to ensure that the classes exposed by the Client Object Model exactly matched the classes within the Server Object Model, the client classes were created using a code-generation tool that examined the Server Object Model for classes that were decorated with the ClientCallableType attribute.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd Protection Status

Share Point 2010 Topics