Adobe AIR verses Internet Explorer

Forum|Forum|8 years ago
February 20, 2017
2 replies
1196 views

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 has been closed for replies.

miker19342147Author

Participating Frequently

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

Has this problem really been around for 7 YEARS?

natural_criticB837

Legend

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

miker19342147Author

Participating Frequently

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.

natural_criticB837

Legend

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.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded