Tom, I noticed similar behavior when I had stipulated an incorrect endpoint for an rtmp channel - it didn't fail over, the app just hung, perhaps due to a runtime error - you could dump the channelFault event and see what you get there. I haven't tested but there is the connectTimeout property which may work. Don't know how you'd implement it via xml.
Jeff -----Original Message----- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Tom Chiverton Sent: Monday, October 15, 2007 6:45 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] secure and non-secure channels for (ColdFusion) remoting Our live server runs both SSL and non-SSL, and we would like Flex applications to connect via SSL if possible, but fall back to non-SSL. Accordingly we set the channels for our destinations up like: <channels> <channel ref="my-cfamf-sec"/> <channel ref="my-cfamf"/> </channels> with the normal channel defs: <channel-definition id="my-cfamf" class="mx.messaging.channels.AMFChannel"> <endpoint uri="http://{server.name}:{server.port}/flex2gateway/"; class="flex.messaging.endpoints.AMFEndpoint"/> <properties> <polling-enabled>false</polling-enabled> <serialization> <instantiate-types>false</instantiate-types> </serialization> </properties> </channel-definition> <channel-definition id="my-cfamf-sec" class="mx.messaging.channels.SecureAMFChannel"> <endpoint uri="https://{server.name}:{server.port}/flex2gateway/"; class="flex.messaging.endpoints.SecureAMFEndpoint"/> <properties> <polling-enabled>false</polling-enabled> <serialization> <instantiate-types>false</instantiate-types> </serialization> </properties> </channel-definition> However, in development application hangs on the first remoteObject call. If we reverse the order of the channels and recompile, the application is fine. This occurs in 2.0.1 hf1 and hf3. There is nothing listening on port 443 on the development systems. If I run the traffic through the WebScarab Java HTTP proxy to try and see what is going on, it works. There is a request for "https://whitbread2.localdomain:443/crossdomain.xml"; which makes sense, so that might be the problem. Is anyone else making this sort of 'auto-degrade' Flex application work ? -- Tom Chiverton **************************************************** This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at St James's Court Brown Street Manchester M2 2JF. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by The Solicitors Regulation Authority. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 8008. For more information about Halliwells LLP visit www.halliwells.com. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links
