ria contact
play

RIA Contact Josh Holmes James Ward Microsoft Evangelist Adobe - PowerPoint PPT Presentation

Architecting RIA Contact Josh Holmes James Ward Microsoft Evangelist Adobe Evangelist josh.holmes@microsoft.com jaward@adobe.com joshholmes.com jamesward.com What is by Kushal Das Is it Rural Inoculation Association? Rare Isotope


  1. Architecting RIA

  2. Contact Josh Holmes James Ward Microsoft Evangelist Adobe Evangelist josh.holmes@microsoft.com jaward@adobe.com joshholmes.com jamesward.com

  3. What is by Kushal Das

  4. Is it… Rural Inoculation Association? Rare Isotope Accelerator? Royal Institute of Acting Rampantly Inept Alien? Royally Idiotic Annoyance? Really Inane Acronym? Rich Internet Application?

  5. Ubiquity Richness Next Generation

  6. What’s different with RIA? new for Desktop Developers new for Web Developer Browser Sandbox Business Logic in UI Hype Back Button and Refresh Non-text based layout Visual Vocabulary Service Orientation State management Animation Limited Runtime Component Level Logic

  7. Taliesin West: Drafting Studio

  8. � MVP Pattern � MVC Pattern � View is more loosely � Controller are based coupled to the model on behaviors and can be shared across � Easier to unit test views � Usually view to � Can be responsible for presenter map one to determining which one view to display (Front � Complex views may Controller Pattern) have multi presenters

  9. 70 20 10 ..but don’t forget the power users

  10. with usability with usability

  11. • Cookies are on a domain level • bar.com cannot access foo.com cookies… • Same domain - http://foo.com is different than http://bar.foo.com or http://www.foo.com • Same protocol - http://foo.com is different than https://foo.com • Same port - http://foo.com is different than http://foo.com:8080 • foo.com should feel secure storing user data in cookies • Prevent cross-site forgery • Exploits a sites trust for a user

  12. • “Private” services (for your own app) • DO use browser-based authentication • Cookies, HTTP Auth, etc. • DO NOT enable public access via cross-domain policy file • “Public” services (for 3rd-party apps) • DO NOT use browser-based authentication • DO publish cross-domain policy files • DO use “cross-domain-safe” authentication • E.g. URL signatures • DO separate public services in their own domain • E.g. api.flickr.com vs. www.flickr.com

  13. by Caution Mike

  14. by billaday

  15. by joeltelling

  16. by mikeyexists

  17. Take-aways � Rich Internet Applications are meant to enhance user experience � Architecture of the client matters � Use good development practices � Leverage the framework � Build for the user � Don’t get religious

  18. Take the Next Step � http://www.joshholmes.com � http://www.jamesward.com

  19. Architecting RIA

  20. Contact Josh Holmes James Ward Microsoft Evangelist Adobe Evangelist josh.holmes@microsoft.com jaward@adobe.com joshholmes.com jamesward.com

Recommend


More recommend