Remoting Service

Defines Remoting Service destinations for working with remote objects.

A Remoting service destination is the object that you connect to using an <mx:RemoteObject> tag or the corresponding ActionScript API.

Sample:

<service id="remoting-service" class="flex.messaging.services.RemotingService" messageTypes="flex.messaging.messages.RemotingMessage">
<!-- Adapter definition is not mandatory the gateway will automatically configure it-->
<adapters>
    <adapter id="dotnet" class="FluorineFx.Remoting.RemotingAdapter" default="true"/>
</adapters>

<default-channels>
    <channel ref="my-amf"/>
</default-channels>
				
<destination id="EchoServiceRO">
<!-- 
  <channels>
     <channel ref="my-amf"/>
  </channels>
-->  
  <properties>
    <source>ServiceLibrary.EchoService</source>
    <!-- <scope>application</scope> -->
  </properties>
  <security>
    <security-constraint ref="privileged-users"/>
  </security>
</destination>

...
<security>
    <security-constraint id="privileged-users">
        <auth-method>Custom</auth-method>
        <roles>
            <role>privilegedusers</role> 
            <role>admins</role>
        </roles> 
    </security-constraint>
</security>
... 
				

Security

Use a security constraint to authenticate and authorize users before allowing them to access a destination (custom authentication supported only).

Security constraints can be declared inline in the destination definition or globally and referenced by their id in a destination definition.

 

Destination adapters

Adapters are server-side components that interact directly with the service object. Adapter definition is not mandatory as the gateway will automatically configure it

 

Remote object properties

Property element	Description
source	Fully qualified type name of the .NET object (the remoting service)
scope	Valid values are request, application, and session. The default value is request. Indicates whether the object is available in the request scope, the application scope, or the session scope. Objects in the request scope are stateless (a remoting service object is instantiated for every request). Objects in the application scope are available to the (web) application that contains the object (a single instance of the remoting service object is created). Objects in the session scope are available to the entire client session (a single remoting service object is created per asp.net session).

 

Web service properties

Not supported

Property element	Description
wsdl	Not supported
soap	Not supported