Since you guys are not providing any support in this forum, where do I go now? Until now I did not see any valid forum in the Apache site what are my options?
the issues that I faced in the recent times were cmpletely related to framewrk internals..lik wifi cnnection etc..whch needs help frm core flex devs...so...im worried about those kind of issues rather than api issues...that's the reason I started the discussion...idon't know if you realized that frame work is a little buggy...i asked a question last week..wasexpecting a little help from adobe guys...with a little research I found out that alexharui is no longer active in this forum...also many of the flex guys..
Sent from my Samsung smartphone on AT&T
I did not check the network monitor as I was not debugging it, i was running the application. Also, can it happen that two Air applications loose the internet connectivity at the same time? I had 2 clients(changed the id in one of the clients app.xml to run two instances on the same machine) and i continuously switching btwn the wirelss and lan, that caused the error in both the clients at the same time.. !
Message was edited by: saisri2k2
Again, this is outside my area of expertise, but I don’t understand the setup. Is there a timer continuously making requests via HTTPService? Or is it that you can switch networks and “much later” make a request and that will fail? What if you use URLLoader instead of HTTPService?
I'm using httpservice here, I have a desktop AIR application which connects to the server and keeps the session going by polling the server every 30-50 seconds. If I go from one network to another ie., Wireless to the ethernet port, and I do this a couple of times, This polling would only give me fault events back. Since we poll every 30 seconds, we always get fault event at the end of the timer. This not only happens to this application, If I have 2 applications open on the same machine which are based on AIR, they both cannot connect to the server at the same point of time.
We have a bunch of issues reported on this issue, only solution so far is it re-launch the application, it some how resets the network connectivity. But, it seems un-reliable as of now.
Could you please ask some one in your Flex team to look into this issue? Thanks, I think it is easy to reproduce if you keep on chaning the network, it might hit you the very first time or 8th or 9th time.