You can create channels dynamically via actionscript like below:
<mx:Script> <![CDATA[ import mx.messaging.ChannelSet; import mx.messaging.Channel; import mx.messaging.channels.AMFChannel; public var cst:ChannelSet; public function initApp():ChannelSet { cst = new ChannelSet(); var customChannel:Channel = new AMFChannel("my-cfamf", "your uri here"); cst.addChannel(customChannel); return cst; } ]]> </mx:Script> <mx:RemoteObject id="goLocalService" channelSet="{initApp()}" destination="ColdFusion" showBusyCursor="true" source=" " /> </mx:RemoteObject> This example is using the canned "Coldfusion" destination that comes with services-config file. You can use FlashVars to pass whatever uri you want based on your environment. This way you don't have to use the services argument in the compiler either. Cheers, Farid ________________________________ From: Jeremy Rottman [mailto:[EMAIL PROTECTED] Sent: Thursday, November 30, 2006 12:30 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] services-config with multiple endpoints We are nearing the end of our flex application development cycle, and about to head into beta testing. Something I have been thinking about for a while now is how we are going to instance the application. One of the things I am looking into is multiple remote object end points. So that if we an end point for each of the sub-domains that are created when we add a new instance. Does anyone know if this is possible? IE having something like this. <endpoint uri="http://instanceID.admin.mydomain.com/flex2gateway/ <http://instanceID.admin.mydomain.com/flex2gateway/> " class="flex.messaging.endpoints.AMFEndpoint"/> <endpoint uri="http://instanceID.user.mydomain.com/flex2gateway/ <http://instanceID.user.mydomain.com/flex2gateway/> " class="flex.messaging.endpoints.AMFEndpoint"/>