Oh yes, I have tried. I tried setting it to zero, and also to a high
number. No dice. IT always timesout in about 23 seconds or so with this
error:
[FaultEvent fault=[RPC Fault faultString=error
faultCode=Channel.Call.Failed faultDetail=NetConnection.Call.Failed:
HTTP: Failed]
Did you attempt using -1 as Douglas suggested?
On Mon, Apr 28, 2008 at 11:59 AM, Cameron Childress [EMAIL PROTECTED]
wrote:
Oh yes, I have tried. I tried setting it to zero, and also to a high
number. No dice. IT always timesout in about 23 seconds or so with this
error:
[FaultEvent
No extra fancy stuff going on. Every remoting call works except this one.
Really, this one works too, but only when CF/Flex Remoting responds ~20/30
seconds. This CF based remoting call is proxying requests from Flex to a
remote server which may sometimes timeout or respond slowly. What I need
Sounds like time to use a RemoteObject. ;-)
Leif
On Mon, Apr 28, 2008 at 2:31 PM, Cameron Childress [EMAIL PROTECTED]
wrote:
Delightful. This looks like a reported bug in AIR.
https://bugs.adobe.com/jira/browse/SDK-15403
-Cameron
On Mon, Apr 28, 2008 at 1:29 PM, Cameron Childress
I'm using a remote object. I would suspect all the network request objects
are effected, and that it may be a problem with the AIR Runtime Player and
not the SDK, since it works on Flex/Flash Player.
-Cameron
On Mon, Apr 28, 2008 at 3:07 PM, Leif Wells [EMAIL PROTECTED] wrote:
Sounds like time
