I have an interesting challenge.
1. I need to have my WRT packaged FL3 application talk to a socket server over WiFi. So far so good all working.
2. My device needs to be told via some parameter what the IP address of the server it is to connect to is. As FL3 allows access to either the network OR local filesystem i need a method to pass the ip. This was done using FlashVars in the html container - so far so good.
3. When published as a widget, for some reason focus is not given to the flash lite app. This can be overcome using a meta refresh tag, but that prevents passing the parameters as all the embed data is lost/not required.
Any ideas on how i can either pass a param, or push focus to my flash lite app?
Item 2 - Odd security FL3 N95
I am also seeing some odd security behaviour here. I have my socket server able to post a response to a security policy request, and also a suitable crossdomain.xml file in the root of my webserver. I am able to see when either are requested.
Previously, when running the app natively (i.e. not in a web-page) I saw a security request for crossdomain.xml on 80. No amount of changing code (perhaps wrongly) enabled this to be moved to the socket (I would prefer this as the html component is protected with http_auth) and as such the user has to key in username and password.
Now, when run within the WRT framework, there is no request at all from either 80 or from my socket server
Confused!!! Anybody can shed some light on either of these - Item 2 is less of an issue as the code works - but to my mind, it shouldn't