RIA is 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. It is a tool while SOA, is the architecture.
All the best Ashraf Galal ----- Original Message ----- From: Michael Poulin To: [email protected] Sent: Wednesday, March 26, 2008 3:44 PM Subject: Re: [service-orientated-architecture] Re: Meehan on RIA meets SOA One of lead architects around me said that SOA and RIA are almost orthogonal because RIA demands fine-grained operations while SOA tends to coarse-grained ones... - Michael ----- Original Message ---- From: Rob Eamon <[EMAIL PROTECTED]> To: [email protected] Sent: Tuesday, March 25, 2008 2:37:30 PM Subject: [service-orientated-architecture] Re: Meehan on RIA meets SOA Why is that? Why would an RIA be "more connected" to services based on the interaction style? Why would accessing services via REST vs. any other mechanism be considered more connected? A service consumer is a service consumer, regardless of the service interface, no? Or are you referring to the relative prevalence of an RIA's use of services compared to other approaches? -Rob --- In service-orientated- architecture@ yahoogroups. com, "Anne Thomas Manes" <[EMAIL PROTECTED] > wrote: > > RIA and mashups will become more intimately connected with SOA > if/when REST becomes a predominant approach for building services. > > Anne ------------------------------------------------------------------------------ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
