Best And Worst Practices Building Ria with Adobe and Microsoft

by Josh Holmes on Nov 17, 2009

4,724 views

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

Less

14 Embeds 1,039

http://www.jamesward.com	770
http://cdmwebguru.blogspot.com	223
http://www.slideshare.net	17
http://www.web2expo.com	11
http://cdmwebguru.blogspot.in	4
http://translate.googleusercontent.com	4
http://www.jamesward.org	3
http://webudget.cayambe.com	1
resource://brief-content	1
applewebdata://11CD9CF8-C782-40EC-BA7E-8A96C6DE8044	1
http://static.slidesharecdn.com	1
http://www.hanrss.com	1
http://localhost	1
http://cdmwebguru.blogspot.com.au	1

More...

Statistics

Favorites: 8
Downloads: 113
Comments: 0
Embed Views: 1,039
Views on SlideShare: 3,685
Total Views: 4,724

Best And Worst Practices Building Ria with Adobe and Microsoft — Presentation Transcript

Best and Worst Practices Building R IA from Adobe and Microsoft

Contact Josh Holmes RIA Evangelist [email_address] joshholmes.com James Ward RIA Evangelist [email_address] jamesward.com

What is by Kushal Das

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

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

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 .

RIAs typically:

run in a web browser , or do not require software installation

run locally in a secure environment called a sandbox

http://en.wikipedia.org/wiki/Rich_Internet_application

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

Ubiquity Richness Next Generation

Tour de Flex

http://www.adobe.com/devnet/flex/tourdeflex/

http://silverlight.net

http://cmafest.com/bethisclose

http://www.iis.net/media/experiencesmoothstreaming1080p

http://mscui.net/patientjourneydemonstrator/

http://linqtotwitter.codeplex.com/

http://www.codeplex.com/

Taliesin West: Drafting Studio

MVP Pattern

View is more loosely coupled to the model

Easier to unit test

Usually view to presenter map one to one

Complex views may have multi presenters

MVC Pattern

Controller are based on behaviors and can be shared across views

Can be responsible for determining which view to display (Front Controller Pattern)

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

with usability

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

“ 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

1.0 minimal Accessibility support

We only provide some root “alt” information

No focus and keyboard support

2.0 Accessibility greatly improved

Full keyboard support

Decorate XAML UI elements with Accessibility info

Add accessibility to custom controls

Accessibility reader support (AT)

Accessibility tree exposition for UIA

Note - UIA on Windows, OS X does not support accessible plug-ins

by Caution Mike

private void Application_Startup( object sender, StartupEventArgs e) { string startPageParameter = "/StartPage" ; if (!e.InitParams.ContainsKey(startPageParameter)) { this .RootVisual = new DefaultStartPage(); } else { switch (e.InitParams[startPageParameter]) { case "DefaultStartPage" : this .RootVisual = new DefaultStartPage(); break ; case "NonDefaultStartPage" : this .RootVisual = new NonDefaultStartPage(); break ; default : throw new Exception ( "/StartPage must be 'DefaultStartPage' or 'NonDefaultStartPage'." ); } } }

by billaday

by joeltelling

by mikeyexists

Best and Worst Practices Building R IA from Adobe and Microsoft

Contact Josh Holmes RIA Evangelist [email_address] joshholmes.com James Ward RIA Evangelist [email_address] jamesward.com

Best And Worst Practices Building Ria with Adobe and Microsoft

by Josh Holmes on Nov 17, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

14 Embeds 1,039

Statistics

Best And Worst Practices Building Ria with Adobe and Microsoft — Presentation Transcript