Datasheet

Client - Side OM
Frequently, developers want to write applications that need to talk to SharePoint from a client
operating system and from client applications, such as the ones in the Offi ce suite. With the addition
of Silverlight integration to SharePoint, a client object model is critical because it makes it easier for
developers to write applications against a full object model, rather than trying to call web services
from within their client applications. Additionally, because Silverlight runs on the client rather
than running server - side, the client Object Model (OM) makes it easier for developers to build
rich Silverlight applications on SharePoint. SharePoint 2007 requires you to write against untyped
web services for remoting your applications. The client object model provides a more productive
development experience since it provides a typesafe environment that works with the Intellisense
in Visual Studio.
Web 2.0 Protocols and New Standards
There are a number of new protocols and standards that SharePoint 2010 implements across its
workloads. Some are considered “ Web 2.0 ” protocols, such as Representational State Transfer
(REST), Asynchronous JavaScript + XML (AJAX), JavaScript Object Notation (JSON) and
ATOMSub/Pub, while others are going through standards validation, such as the Content
Management Interoperability Services (CMIS). SharePoint still continues to support other standards
such as WebDAV and web services. Adding these newer protocols and standards allows SharePoint
to interoperate with other systems more easily, whether it is to create mash - ups between systems
hosted in SharePoint or to allow data interoperability between systems.
Sandbox Solutions and Resource Governors
One of the biggest downsides to developing custom solutions in SharePoint 2007 is the requirement
for the solution developer to be an administrator on the server. Often, IT administrators will
not allow developers to access the server with the elevated privileges they need to deploy their
solution, as custom web parts or other SharePoint solutions require that you place your code in
the global assembly cache (GAC) or in the fi le system related to your SharePoint site. Plus, the
administrator has no simple way to ensure that badly written code does not slow down the system,
crash it, or perform malicious activities. You could implement code access security (CAS), but that
requires the developer to write the code to implement it; in addition, managing CAS policies is not
a simple task.
However, with SharePoint 2010, there is a new feature called Sandbox Solutions that allows
for the deployment of SharePoint solutions inside a secure environment hosted in SharePoint.
Because it is a secure environment, the IT administrator can control who can deploy solutions
and how many resources these solutions receive through the new resource governors built into
the system. For example, if a custom - developed solution is using too many CPU resources,
SharePoint will automatically stop running the solution. That said, today the Sandbox Solution
offers only a subset of the SharePoint object model, so while it might be a good solution for
some custom applications, you will have to evaluate if there is enough functionality to meet your
application needs.
What ’ s New in the SharePoint Platform and Tools
❘
3
CH001.indd 3CH001.indd 3 4/5/10 4:19:13 PM4/5/10 4:19:13 PM