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.

Best And Worst Practices Building Ria with Adobe and Microsoft

6,005 views

Published on

Come listen to leading Rich Internet Applications (RIA) experts from Microsoft and Adobe discuss many of the best and worst practices when building RIAs. RIAs provide a similar user experience to traditional desktop applications combined with the ease of deployment of web/browser based applications. This produces a fair amount of confusion because there are a number of potentially conflicting practices depending on whether you approach your RIA as a desktop or a web application. This session dives into the definition of RIA and walks through the best and worst practices that have appeared over and over again. We will explore architectural patterns and practices such as state management, fault tolerance, service composition, communications protocols and message formats and goes into details on how RIAs can be developed using runtime environments such as Adobe AIR or Microsoft Silverlight.

For more read our blogs at
http://www.jamesward.com
http://www.joshholmes.com

Published in: Technology
  • Be the first to comment

Best And Worst Practices Building Ria with Adobe and Microsoft

  1. 1. Best and Worst Practices Building R IA from Adobe and Microsoft
  2. 2. Contact Josh Holmes RIA Evangelist [email_address] joshholmes.com James Ward RIA Evangelist [email_address] jamesward.com
  3. 3. What is by Kushal Das
  4. 4. RIA for me is all about expanding the experience for the user. Those "gray beards" amongst us remember the old days of just being happy seeing plain, static text show up in the browser . We've come a long way since then. While dynamic web sites have pushed us way beyond the simple pages of the old days, RIA is helping us now provide the same level of dynamic interaction on the client side as well. I think this is wonderful as it improves the entire process (server and client)! While we have a great opportunity here to help users, the challenge is to not actually make things more difficult . Like any new feature, the web is rife with examples of poorly designed and hard to use applications. It is not enough to learn how to make HTTP requests and change content dynamically, but rather how to do it well in ways that help the user and not scare them off. Raymond Camden http://www.insideria.com/2008/01/what-is-ria-1.html
  5. 5. But the term still begs the question: Rich in what sense? Responsiveness, immediacy, convenience? production values, chrome, animation? http://www.insideria.com/2008/01/what-is-ria-1.html Christian Crumlish
  6. 6. <ul><li>Rich Internet applications (RIA) are web applications that have the features and functionality of traditional desktop applications . RIAs typically transfer the processing necessary for the user interface to the web client but keep the bulk of the data (i.e., maintaining the state of the program, the data, etc.) back on the application server . </li></ul><ul><li>RIAs typically: </li></ul><ul><li>run in a web browser , or do not require software installation </li></ul><ul><li>run locally in a secure environment called a sandbox </li></ul>http://en.wikipedia.org/wiki/Rich_Internet_application
  7. 7. Back Button and Refresh Visual Vocabulary State management Browser Sandbox Business Logic in UI Component Level Logic Animation new for Desktop Developers new for Web Developer What’s different with RIA? Limited Runtime Service Orientation Non-text based layout Hype
  8. 8. Ubiquity Richness Next Generation
  9. 9. <ul><li>Tour de Flex </li></ul><ul><li>http://www.adobe.com/devnet/flex/tourdeflex/ </li></ul>
  10. 10. <ul><li>http://silverlight.net </li></ul><ul><li>http://cmafest.com/bethisclose </li></ul><ul><li>http://www.iis.net/media/experiencesmoothstreaming1080p </li></ul><ul><li>http://mscui.net/patientjourneydemonstrator/ </li></ul><ul><li>http://linqtotwitter.codeplex.com/ </li></ul><ul><li>http://www.codeplex.com/ </li></ul>
  11. 15. Taliesin West: Drafting Studio
  12. 18. <ul><li>MVP Pattern </li></ul><ul><ul><li>View is more loosely coupled to the model </li></ul></ul><ul><ul><li>Easier to unit test </li></ul></ul><ul><ul><li>Usually view to presenter map one to one </li></ul></ul><ul><ul><li>Complex views may have multi presenters  </li></ul></ul><ul><li>MVC Pattern </li></ul><ul><ul><li>Controller are based on behaviors and can be shared across views </li></ul></ul><ul><ul><li>Can be responsible for determining which view to display (Front Controller Pattern) </li></ul></ul>
  13. 28. ..but don’t forget the power users 70 20 10
  14. 35. with usability
  15. 36. <ul><li>Cookies are on a domain level </li></ul><ul><ul><li>bar.com cannot access foo.com cookies… </li></ul></ul><ul><ul><li>Same domain - http://foo.com  is different than http://bar.foo.com or http://www.foo.com </li></ul></ul><ul><ul><li>Same protocol - http://foo.com is different than https://foo.com </li></ul></ul><ul><ul><li>Same port - http://foo.com is different than http://foo.com:8080 </li></ul></ul><ul><li>foo.com should feel secure storing user data in cookies </li></ul><ul><li>Prevent cross-site forgery </li></ul><ul><ul><li>Exploits a sites trust for a user </li></ul></ul>
  16. 38. <ul><li>“ Private” services (for your own app) </li></ul><ul><ul><li>DO use browser-based authentication </li></ul></ul><ul><ul><li>Cookies, HTTP Auth, etc. </li></ul></ul><ul><ul><li>DO NOT enable public access via cross-domain policy file </li></ul></ul><ul><li>“ Public” services (for 3rd-party apps) </li></ul><ul><ul><li>DO NOT use browser-based authentication </li></ul></ul><ul><ul><li>DO publish cross-domain policy files </li></ul></ul><ul><ul><li>DO use “cross-domain-safe” authentication </li></ul></ul><ul><ul><li>E.g. URL signatures </li></ul></ul><ul><li>DO separate public services in their own domain </li></ul><ul><ul><li>E.g. api.flickr.com vs. www.flickr.com </li></ul></ul>
  17. 45. <ul><li>1.0 minimal Accessibility support </li></ul><ul><ul><li>We only provide some root “alt” information </li></ul></ul><ul><ul><li>No focus and keyboard support </li></ul></ul><ul><li>2.0 Accessibility greatly improved </li></ul><ul><ul><li>Full keyboard support </li></ul></ul><ul><ul><li>Decorate XAML UI elements with Accessibility info </li></ul></ul><ul><ul><li>Add accessibility to custom controls </li></ul></ul><ul><ul><li>Accessibility reader support (AT) </li></ul></ul><ul><ul><li>Accessibility tree exposition for UIA </li></ul></ul><ul><li>Note - UIA on Windows, OS X does not support accessible plug-ins </li></ul>
  18. 49. by Caution Mike
  19. 52. private void Application_Startup( object sender, StartupEventArgs e) { string startPageParameter = &quot;/StartPage&quot; ; if (!e.InitParams.ContainsKey(startPageParameter)) { this .RootVisual = new DefaultStartPage(); } else { switch (e.InitParams[startPageParameter]) { case &quot;DefaultStartPage&quot; : this .RootVisual = new DefaultStartPage(); break ; case &quot;NonDefaultStartPage&quot; : this .RootVisual = new NonDefaultStartPage(); break ; default : throw new Exception ( &quot;/StartPage must be 'DefaultStartPage' or 'NonDefaultStartPage'.&quot; ); } } }
  20. 56. by billaday
  21. 65. by joeltelling
  22. 73. by mikeyexists
  23. 77. Best and Worst Practices Building R IA from Adobe and Microsoft
  24. 78. Contact Josh Holmes RIA Evangelist [email_address] joshholmes.com James Ward RIA Evangelist [email_address] jamesward.com

×