Yes, it brings application integration to the client so that you can create the effect of client-side portals. If you have a client that knows a great deal about local resources, local data, local services as well as remote resources, remote data, remote services, then you have the ability to integrate these and orchestrate these in very interesting client-side workflows. A client that understands protocols such as XML-RPC and SOAP in addition to basic HTTP can aggregate Web services in a sort of flow so that the input and output of one Web service can be funnelled to the next, essentially creating OLE for the Web, a way of cut and pasting data from one Web service, or even a portion of data from one Web service into another so that you can aggregate say a service that say locates MP3's with a service that automatically searches for CD's on Amazon.com using its Web service and also with another Web service that finds recent blog entries on that MP3, maybe even based on context that suggest where your longitude and latitude so that you can find out if this band's performing in your area and so on and so forth. So these are client-side aggregation of remote services as well as some local services. So client-side aggregation and data aggregation, breaking down the Web application Silos, is a big part of Rich Internet Applications. It's not just about putting a new face on existing Web applications. It does involve thinking in a slightly new way about service composition.