I tried the timeout, but it did not have any effect. So, I'm trying to figure out if it's a problem with one of the following:
1) flash player 2) AMFPHP working with Flex 3 3) Cairngorm on Flex 3 4) Flex 3 SDK 5) Some browser related issue Like I say, it works with Flex 2 sdk, so I'm at a loss... I think it's even stranger that nobody else has ever had this problem. Any other ideas? Is there any way to force a disconnection/reconnection after a freeze? Thanks, -Todd --- In flexcoders@yahoogroups.com, "valdhor" <[EMAIL PROTECTED]> wrote: > > Actually no. > > I do a lot of AMFPHP RemoteObject calls in my application and have > never had this problem. > > There are two things you mention in your post that are different here... > > 1. My application is only used on an intranet so all connections are > fast. > > 2. I am not using Cairngorm at the moment. > > Whether one of these is the root cause I cannot say. > > One thing you may like to do is set a timeout value. When the call > times out, in your fault handler try to disconnect the connection and > then retry (Or alert the user). > > <mx:RemoteObject id="blah" source="foo" destination="amfphp" > fault="faultHandler(event)" showBusyCursor="false" requestTimeout="10"> > > private function faultHandler(fault:FaultEvent):void > { > switch(fault.fault.faultCode.toString()) > { > case "Client.Error.RequestTimeout": > blah.disconnect(); > Alert.show("The server is not responding. Please check > that you are connected and the server is running.", "Server Timeout"); > break; > default: > Alert.show(fault.fault.faultString, > fault.fault.faultCode.toString()); > break; > } > } > > > > > --- In flexcoders@yahoogroups.com, "supertodda" <todd@> wrote: > > > > Anybody out there experiencing this issue in flex 3 with AMFPHP? > > >