Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Connecting to Data from Windows Phone 8

You know you have to have a great experience when you develop your Windows Phone 8 applications right? The greatest experience you can give your users is around their data. There are ways to improve your Windows Phone 8 application and Chris Woodruff will teach you how to get data quickly, save it with validation, save it locally and many, many more tricks. Come see why you should know the tricks of the trade before developing that killer Windows Phone 8 app. You will be a Data Experience expert when you leave the room after this session.

  • Be the first to comment

  • Be the first to like this

Connecting to Data from Windows Phone 8

  1. 1. Connecting to Data fromWindows Phone 8Chris WoodruffSenior TrainerTelerikLevel: Intermediate to Advanced
  2. 2. Who I am?Chris WoodruffMVP, Visual C#Trainer at TelerikCo-host of Deep Fried Bytes Podcast@cwoodruff / cwoodruff@live.com /Skype: cwoodruff
  3. 3. You will learn:• Understand the benefits of using REST webservices for your mobile apps• Be able to use develop solutions againstOData that will give better experiences foryour users• How to shape your data queries to give thebest performance for your mobile apps• A glimpse into using Windows Azure MobileServices to also get to your data in the cloud.
  4. 4. LETS TAKE A REST
  5. 5. • REST is an architectural style fordistributed hypermedia systems• REpresentational State Transfer• The term originated in 2000 by RoyFielding for his PhD thesis• REST states that the existing protocolsand principles of the web are enough tocreate robust Web Services – no SOAPis neededWhat is REST?
  6. 6. What does REST consist of?REST is a very simple architecture:• Application state and functionality isdivided into resources.• Every resource is uniquely addressableusing a universal syntax for hypermedialinks• All resources share a uniform interface forthe transfer of state between a client and aresource
  7. 7. What does REST consist of?Characteristics of REST• Client–server• Stateless• Cacheable• Uniform Interface• Named Resources• InterconnectedResourceRepresentations• Layered SystemOperations of REST• GET• POST• PUT• DELETE
  8. 8. Example of RESTQuery a Resourcehttp://www.parts-depot.com/parts/getPart?id=00345http://www.parts-depot.com/parts/00345http://restbucks.com/PlaceOrder?coffee={type}&size={size}&milk={milk}&location={location}
  9. 9. DIGGING INTO ODATA
  10. 10. Open Data Protocol (OData)• “RESTful” Web protocol• Designed to work with data across HTTP• Built on existing Web standards• Uses popular formats to return datapayloads to consumer• Uses self-describing metadata• Has multiple options to buildimplementation based on standardprotocol• Soon to be a full web standard
  11. 11. The Basics• Feeds, which are Collections oftyped Entries• OData services can exposeService Operations• OData services expose all theseconstructs via URIs• OData service may also expose aService Metadata Document
  12. 12. Full SQL like Query “Language”HTTP Command(Verb)SQLCommandGET SELECTPUT UPDATEPOST INSERTDELETE DELETE
  13. 13. http://services.odata.org/OData/OData.svc_______________________________________/|service root URIhttp://services.odata.org/OData/OData.svc/Category(1)/Products?$top=2&$orderby=name_______________________________________/ __________________/_________________/| | |service root URI resource path query optionsWhat is a URI?
  14. 14. OData Best Practices (Producer)• Always design your OData feed willserver-side paging if your entitycollections hold large amounts of data.• Looks at server-side validation of queriesand data updates based on the usercredentials sent through HTTP
  15. 15. Why are we excited!!
  16. 16. ODATA AND HOW TOCONSUME IT IN WINDOWSPHONE
  17. 17. DEMOWindows Phone and OData
  18. 18. OData Best Practices (Consumer)• Use Query Projection to only bring backthe entity properties you or your appneeds.• Think about client-side paging even if theirexists server-side paging.• Design and implement a client-side datacaching function in your app (unlesssensitive data).
  19. 19. AZURE MOBILE SERVICESAND HOW TO CONSUME ITIN WINDOWS PHONE
  20. 20. DEMOWindows Phone and Azure Windows Services
  21. 21. The demo projects can be found at:github.com/cwoodruff/
  22. 22. ResourcesRESThttp://www.ics.uci.edu/~taylor/documents/2002-REST-TOIT.pdfODatahttp://odata.orghttp://odataprimer.comAzure Mobile Serviceshttp://www.windowsazure.com/en-us/develop/mobile/
  23. 23. Contact MeChris “Woody” Woodruffcwoodruff@live.comTwitter @cwoodruffSkype cwoodruffhttp://chriswoodruff.comhttp://deepfriedbytes.com

×