--- In [email protected], "Anil John" <[EMAIL PROTECTED]> wrote: > > There seems to a bit of confusion (perhaps in my own mind) regarding > what is meant by a RIA. To me a RIA is a presentation tier > technology/approach the combines the reach of the web with the richness > of traditional rich client apps.. Examples would be AJAX, Flash, Java > plug-in's, Microsoft's Silverlight etc. > > While these technologies can be used to build the UIs for solutions that > use SO approaches, RIAs have no dependency on SOA.
Yes, absolutely. However, a typical RIA would depend on some server-side component and many typical web applications are data-entry components that essentially manipulate documents on the server. In that case, how can we make it easy for users to do so Enterprise DIY and/or replicate the mashup phenomenon inside IT departments? > >I used REST for my web applications but I consider it to be a simpler > subset of SOA > > ... and we are off to the races... again! :-) Oops! Didn't mean to in any way address that debate. Whatever you use on the server SOA, REST, blah (I'll call it a service) what's the best way to use that as part of an RIA? Thx, -Ashish
