Skip to main content
miker19342147
Participating Frequently
Feb 20, 2017 11:49 PM UTC
Question

Adobe AIR verses Internet Explorer

We have developed an Adobe AIR application that we point to the URL of our flash web application. We are seeing differences in the communication behavior of our web application with the Adobe AIR container verses Internet Explorer. We are seeing some communication drops fro the Adobe AIR container in our requests back to the web server for requests that take a longer time. Internet Explorer seems to be much more tolerant and handles much better.

Today I was debugging some processing on the web server. I observed that Internet Explorer would wait nicely for my debugging. When I attempted the same thing with the Adobe AIR Container, it fails in the communications.

As I missing some configuration of the Adobe AIR container? 

This topic is closed to new replies. Start a new post to keep the conversation going.

8 replies

miker19342147
Participating Frequently
Mar 1, 2017 8:54 PM UTC

I am looking at this link....AIR RemoteObject timeout in Windows - Is There A Solution???

Has this problem really been around for 7 YEARS?

Translate
natural_criticB837
Legend
Feb 23, 2017 11:12 PM UTC

Hmm I think you can set a timeout on the URLRequest, no?

Translate
miker19342147
Participating Frequently
Feb 23, 2017 11:15 PM UTC

The exact same flash code is running in both Internet Explorer and Adobe Air. So I don't think it is in the code and more flash environmental, unless of course there are different default behaviors.

Translate
natural_criticB837
Legend
Feb 24, 2017 9:45 AM UTC

I was on the mobile earlier, so I couldn't look this up and thought I'd just give you a direction. So let me google this for you:

Flash Player uses the browser to execute URL requests and uses the same timeouts as your browser. In Air you can use URLRequest.idleTimeout to specify your own timeout.

Translate