Skip to main content
Jun 12, 2011 12:48 PM UTC
Question

URL Requests on document ready state issue

Hi,

After resolving a long term connection issue with Air and our server by opting for the native air URL objects (see http://forums.adobe.com/message/3727567#3727567), we've hit another problem.

Now we are experiencing an issue when the app initially boots, and attempts a call to the server, the Service Monitor reports the server unavailable, which is incorrect. An immediate manual trigger of the server check after boot tells us that the server is available.

It seems that Air has not yet initialised whatever is needed to make the call to the server. As a result, any initial call to the server during $(document).ready(), gets a Service Unavailable.

Is there anything that we can do to initialize Air's connections on boot so we don't hit this issue?

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

6 replies

Jun 14, 2011 4:07 PM UTC

We've found that including the Introspector file solves this issue.

Can ANYONE shed light on what is happening. It sounds like something needs to be initialised before any external calls are made.

Translate
chris.campbell
Legend
Jun 14, 2011 5:08 PM UTC

I'm asking around.  I'll post back once I find more info.

Chris

Translate
chris.campbell
Legend
Jun 14, 2011 6:00 PM UTC

Out of curiousity, where are you calling the monitor call?  Is it in applicationComplete?  creationComplete?  Somewhere else?

Thanks,

Chris

Translate
Jun 14, 2011 3:40 PM UTC

Does anyone have a response to this or any suggestions?

Translate