Microsoft has release REST interface in
SharePoint 2013. As a SharePoint solution architect you will be having more
than one options to manipulate SharePoint data in your client applications.
With the REST interface in SharePoint 2013,
folks are asking about what are the differences? And what are the benefits over
each other? I will list all my insights in this blog post.
1) The main difference between Client Object
Model API (COM) than REST API that it requires SharePoint Client assemblies
that’s only available for .NET technologies. While using the REST API doesn’t
require any .NET assemblies to be references in your client application but use
any programming language to execute standard HTTP requests.
using iOS or Android devices, then the REST API is the way to go. While if you
are developing SharePoint 2013 solution on a windows phone 8 then still you
have 2 options either REST or Client Object Model while I recommend to go with
the REST for portability and code-reuse purposes specially if you plan to have
different version of your application on iOS & Android platforms.
will be smaller when you use REST since you don’t need to add any assemblies in
Application server and has HTTP endpoint; you can access it through the
requires you to get an access token to access SharePoint 2013 REST API, Is
there an alternative?
your complete reference to code this.
and Site scope CRUD operations but it is also available on BCS, Search, and
Social Features in SharePoint 2013. Check out these urls:
Using Search REST service:
SharePoint 2013 REST API. It is a great shift to the web standards and to eliminate
the boundaries to integrate SharePoint with Non-Microsoft platforms and tools.
Developers and System integrators toward SharePoint Hybrid Solutions.