| Getting Started with Flex 2 > Flex Basics > Building a Flex Data Services Application > About RPC services | |||
|
|||
|
|||
|
|||
Flex Data Services includes a Remoting Service and a Proxy Service for configuring RPC services. These features build on the RPC services available in the Flex 2 SDK.
You can use Flex 2 SDK without Flex Data Services to create applications that call HTTP services or web services directly without going through a server-side proxy service. You cannot use RemoteObject components without Flex Data Services. By default, Flash Player does not allow an application to receive data from a domain other than the domain from which the application was served. Therefore, an RPC service must either be in the same domain as the server hosting your application, or the remote server that hosts the RPC service must define a crossdomain.xml file.
A crossdomain.xml file is an XML file that provides a way for a server to indicate that its data and documents are available to SWF files served from certain domains, or from all domains. The crossdomain.xml file must be in the web root of the server that the Flex application is contacting.
Use Flex Data Services when you want to provide enterprise functionality, such as proxying of service traffic from different domains, client authentication, whitelists of permitted RPC service URLs, server-side logging, localization support, and centralized management of RPC services. Flex Data Services also lets you use RemoteObject components to access remote Java objects without configuring them as SOAP-compliant web services.
When you use Flex Data Services, instead of contacting services directly, RPC service components contact destinations. Destinations are manageable service endpoints that you manage through a server-side XML-based configuration file.
Flex 2
Send me an e-mail when comments are added to this page | Comment Report
Current page: http://livedocs.adobe.com/flex/2/docs/00000044.html