Alex,
 
I can see their viewpoint.  What would be handy instead, I suppose,
would be the ability to update an application without having to pull
over the entire AIR file - just update a certain resource in the
package.  This would IMO provide a better user experience. 
 
Jeff

        -----Original Message-----
        From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Alex Harui
        Sent: Tuesday, November 06, 2007 4:15 PM
        To: [email protected]
        Subject: RE: [flexcoders] AIR & Modules - I've hit a wall
        
        

        The security folks have deemed that all modules must be
installed in the same AIR package as the application.  SWFs from outside
the package are considered cross-domain and you can't import load them.

         

        
________________________________


        From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Battershall, Jeff
        Sent: Tuesday, November 06, 2007 6:15 AM
        To: [email protected]
        Subject: [flexcoders] AIR & Modules - I've hit a wall

         

        Sorry for the cross-post, but I'm trying to get some more
exposure for
        this issue in hopes of a resolution/workaround.
        
        My desired deployment model for my AIR app is a shell app that
loads
        Modules dynamically. What I'm running into is that the only
location
        that AIR will let me load a module from is from the app-resource
        directory. The problem here is that I cannot programmatically
update
        modules, as I am not allowed to write to the app-resource
directory. And
        any attempts to load my modules from a server fail with "SWF is
not a
        loadable module". I've tried crossdomain.xml on the server side,
but no
        dice. I've tried writing my modules to the app-storage
directory, which
        I can do, but any attempts to load from this directory are met
with the
        same error.
        
        Why does crossdomain.xml fail? Is it because the AIR app doesn't
have a
        domain per se? Tracing
ApplicationDomain.currentDomain.parentDomain
        returns null. 
        
        It would be nice to have at least a workaround, and to know that
this is
        a bug that will be addressed. All input appreciated.
        
        Jeff Battershall
        Application Architect
        Dow Jones Indexes
        [EMAIL PROTECTED]
<mailto:jeff.battershall%40dowjones.com> 
        (609) 520-5637 (p)
        (484) 477-9900 (c)

        

         

Reply via email to