This document discusses various options for accessing data between a remote web application and a SharePoint host, including .NET Client Side Object Model (CSOM), Server REST, JavaScript CSOM, JavaScript REST, web proxy JavaScript CSOM, web proxy REST, and a custom proxy page. It provides demos and discusses the pros and cons of each approach, such as performance, code protection, and testability. The document recommends analyzing your specific requirements to determine the best data access method for your needs based on the tradeoffs involved.

1. SharePoint apps:
data access options
by SERGEI SERGEEV, SHAREPOINT DEVELOPER

2. Agenda
1. Review possible data access options
(remote to SharePoint and SharePoint
to remote).
2. DEMOs.
3. Pros & cons for each option.
4. How to select right data access option.

3. List of different data access options
Remote web to SharePoint host
.NET CSOM
Server REST
JavaScript CSOM
JavaScript REST
SharePoint host to remote web
Web Proxy JSOM
Web Proxy REST
Custom Proxy page
BONUS – Azure AD

4. Remote web to host
DEMO
.NET CSOM vs server REST

5. Remote web to host .NET CSOM
PROS
+ .NET code
+ results as objects
+ batch calls
+ app only context
+ code protection (reverse
engineering)
+ remote events (.NET)
CONS
- .NET code only
- testability
- performance (vs cross-
domain library)
- portability
- results as objects

6. Remote web to host server REST
PROS
+ any language
+ JSON, XML
+ testability
+ app only context
+ portability
+ code protection (reverse
engineering)
+ remote events (.NET)
CONS
- performance (vs cross-domain
library)
- no batch support?
- CSOM isn’t fully covered

7. REST API batching implemented!
Office 365 Roadmap

8. Enable batching support for the REST API

9. Cross-domain library (SP.RequestExecutor.js)
- same origin policy
- allows to perform cross domain calls

10. Cross-domain library. How it works

11. Remote web to host
DEMO
JavaScript CSOM vs client REST
(cross-domain library)

12. Cross-domain library (SP.RequestExecutor.js)
- not an original (xdomain.js)
- alternatives (cors, jsonp)

14. Remote web to host JavaScript CSOM
and client REST
PROS
+ fast
+ testability?
+ portability
+ allows to bypass firewall
behind remote app and
SharePoint
CONS
- no app only context
- no remote events
- intellectual protection
- IE security zones (link)

15. IE security zone issue

16. IE security zone issue

17. App web to remote web (web proxy).
How it works

18. App web to remote web (web proxy)
DEMO
JavaScript CSOM vs client REST
(web proxy)

19. App web to remote web (web proxy)
Prerequisites:
AppManifest’s Remote Endpoints
You can chose your own method, cors, jsonp (if you
can access the server)

20. App web to remote web (web proxy)
PROS
+ fast to SharePoint (you are
in the app web domain
already)
+ testability?
+ portability
CONS
- can be slow
- no authentication
- response limit – 200kb (can be
customized for on premise)
- remote endpoint should be
publicly available
- ports limit – 80, 43, 7000-10000

21. App web to remote web (custom proxy page)
DEMO
Access remote web data through
custom proxy page

22. App web to remote web (custom proxy page)
PROS
+ fast to SharePoint (you are
in the app web domain
already)
+ fast to remote web
(because of iframe)
+ testability
CONS
- IE security zones (link)
- no app only context
- no remote events
- intellectual protection

23. Remote web to host with SharePoint hosted
app
DEMO
Access SharePoint data from remote
web with SharePoint hosted app

24. BONUS. Azure AD
DEMO
Windows Forms SharePoint app

25. What method is right for me?
It depends:
- analyze your requirements
- keep in mind all cons & pros for
every method

26. Questions?

27. Thanks!