The most common way to use RemoteServices in flex is by creating a separate file to keep the configuration, and adding the “-services” switch to the compiler arguments. It’s a good way to do it, but not always, and is especially painful when explaining remoting to someone. But you can skip the whole file and configure the same thing using MXML tags. I’ll take a sample “services_config” file (this one is for zend_amf) and translate it to MXML.

<?xml version="1.0" encoding="UTF-8"?>
<services-config>
    <services>
        <service id="amfphp-flashremoting-service"
        class="flex.messaging.services.RemotingService"
        messageTypes="flex.messaging.messages.RemotingMessage">
            <destination id="zend">
                <channels>
                    <channel ref="library"/>
                </channels>
                <properties>
                    <source>*</source>
                </properties>
            </destination>
        </service>      
    </services>  
    <channels>  
         <channel-definition id="library"
            class="mx.messaging.channels.AMFChannel" >
         <endpoint uri="http://localhost/librarySample/amf.php"
            class="flex.messaging.endpoints.AMFEndpoint" />
        </channel-definition>        
    </channels>
</services-config>

translates to:

<mx:ChannelSet id="chanelSet" >
      <mx:AMFChannel
      uri="http://localhost/librarySample/sampleamf.php" />
</mx:ChannelSet>

<mx:RemoteObject  
      channelSet="{chanelSet}" >       
 </mx:RemoteObject>

So what you need to do is create a ChannelSet, put a channel inside (in this case AMFChannel) and set its uri to the one you would usually put as endpoint uri in the config file.
Once you do that you can start using your RemoteObjects without the services_config.

Of course you should add the rest of the things you usually put inside a remote object. For people who would like an example:

<mx:RemoteObject  
        channelSet="{chanelSet}"
        source="myServerSideClassName"  
        destination="zend" >
        <mx:method
            name="serverSideFunctionName"
            result="someResultFunction()" />           
</mx:RemoteObject>