Managed object model: It is important to be aware that you control when the SharePoint Foundation 2010 managed client object model starts sending the XML to the server and receives the JSON back from the server. The bundling of multiple method calls into a single call to the server is dictated by the realities of network speed, network latency, and desired performance characteristics. If the SharePoint Foundation 2010 managed client object model interacted with the server at every method call, the performance of the system, and the increased network traffic would make the system unworkable. As I mentioned, you explicitly control when the SharePoint Foundation 2010 managed client object model bundles method calls and sends a request to the server. As part of this process, before starting the interaction with the server, you must explicitly specify what content you want to retrieve from the server. This is the biggest difference between the SharePoint Foundation 2010 managed client object model and the SharePoint Foundation 2010 object model. But after you understand the model, it is not challenging. The easiest way to start understanding the difference is to see a simple application.
Best SharePoint Interview Questions and Answers with topic wise:
Webparts & Webparts1 | Event Receivers | Event Receivers1 | Workflows: | MasterPages & MasterPage1| Content Database | Common Real-time issues | Permissions | SPQuery vs. SPSiteDataQuery | ListVsLibrary | ListVsLibrary2 | Content Types | Pages | ListVsLibrary2 | PowerShell |
Interview Questions administrator
Best SharePoint administrator Interview Questions and Answers with topic wise:
Recycle Bin | MMS | ManagedVsCrawledProperties |