It depends completely on how those companies defined SOA. Since there is no single, consensus definition, there is no reasonable conclusion to be drawn, IMO.
For those where SOA == WS (or less specifically, SOA as application architecture or technical infrastructure), they would likely say there is high interaction. For those where SOA is a business level concern, or where SOA is an architecural style and not a distinct architecture level in and of itself, RIA is simply a service consumer candidate. RIAs may benefit from the availability of services, but it is likely that they will need to support other types of components as well--not everything will be a service. But this isn't any different from any other user interface component (which is often not considered to be a service itself). It wouldn't seem that RIA introduces any new constraints or clarifications for any architecture level above application architecture. -Rob --- In [email protected], "Gervas Douglas" <[EMAIL PROTECTED]> wrote: > > Just how relevant do you think RIA is to SOA and vice versa? > > Gervas >
