[flexcoders] Re: Detecing AIR Network Timeout - Best Practices

2009-09-23 Thread reflexactions
We use an error handler on the Operation and then resend up to 3 times before 
raising a hard fail. 

--- In flexcoders@yahoogroups.com, Battershall, Jeff jeff.battersh...@... 
wrote:

 Thanks Alban,
 
 That would work from a 'brute force' type of approach, but doesn't address 
 the scenario of the user interacting with an app but not making network 
 calls, and then encountering an exception when they attempt a network call 
 and the network has timed out.
 
 You could conceivably keep the network connection alive by periodic calls to 
 the back end, but then you're using resources without need. I'd prefer to 
 close the app when the network times out. Just a question of what event to 
 listen to.  
 
 Jeff
 
 -Original Message-
 From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On 
 Behalf Of b_productiv2000
 Sent: Wednesday, September 23, 2009 3:50 AM
 To: flexcoders@yahoogroups.com
 Subject: Re: [flexcoders] Detecing AIR Network Timeout - Best Practices
 
 You've got an example in Tour de Flex named detecting user 
 presence, it is place in the menu AIR capabilities  coding 
 technique.
 
 I don't know if it will serve you but when i read your message i 
 remember this demo.
 
 Alban
 
 Battershall, Jeff a écrit :
  
  
  In the AIR app I'm building, if the user leaves the app running for 
  without interaction, the network times out and the user gets 
  ChannelCall.Failed error when they next attempt to interact with the 
  application.
  
   
  
  What's the best way to listen for a timeout? On the ChannelSet? Or to 
  keep the network connection alive by periodic requests?
  
   
  
  Jeff Battershall
 
 
 
 
 
 
 --
 Flexcoders Mailing List
 FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
 Alternative FAQ location: 
 https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847
 Search Archives: 
 http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links





RE: [flexcoders] Re: Detecing AIR Network Timeout - Best Practices

2009-09-23 Thread Battershall, Jeff
Well I'm not sure that's going to work in my implementation. I'm using 
Cairngorm and my ServiceLocator is holding my RemoteObject instances. I'm 
assuming that's what's timing out.  I suppose I could refresh the RO in 
question and re-try the call, but I'm understanding of the architecture is not 
complete - not sure if that's going to cut it either.

-Original Message-
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf 
Of reflexactions
Sent: Wednesday, September 23, 2009 10:08 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Detecing AIR Network Timeout - Best Practices

We use an error handler on the Operation and then resend up to 3 times before 
raising a hard fail. 

--- In flexcoders@yahoogroups.com, Battershall, Jeff jeff.battersh...@... 
wrote:

 Thanks Alban,
 
 That would work from a 'brute force' type of approach, but doesn't address 
 the scenario of the user interacting with an app but not making network 
 calls, and then encountering an exception when they attempt a network call 
 and the network has timed out.
 
 You could conceivably keep the network connection alive by periodic calls to 
 the back end, but then you're using resources without need. I'd prefer to 
 close the app when the network times out. Just a question of what event to 
 listen to.  
 
 Jeff
 
 -Original Message-
 From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On 
 Behalf Of b_productiv2000
 Sent: Wednesday, September 23, 2009 3:50 AM
 To: flexcoders@yahoogroups.com
 Subject: Re: [flexcoders] Detecing AIR Network Timeout - Best Practices
 
 You've got an example in Tour de Flex named detecting user 
 presence, it is place in the menu AIR capabilities  coding 
 technique.
 
 I don't know if it will serve you but when i read your message i 
 remember this demo.
 
 Alban
 
 Battershall, Jeff a écrit :
  
  
  In the AIR app I'm building, if the user leaves the app running for 
  without interaction, the network times out and the user gets 
  ChannelCall.Failed error when they next attempt to interact with the 
  application.
  
   
  
  What's the best way to listen for a timeout? On the ChannelSet? Or to 
  keep the network connection alive by periodic requests?
  
   
  
  Jeff Battershall
 
 
 
 
 
 
 --
 Flexcoders Mailing List
 FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
 Alternative FAQ location: 
 https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847
 Search Archives: 
 http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links







--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Alternative FAQ location: 
https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! 
Groups Links