I was thinking of the following approach to keep things up to date. The 
applications all talk to the application server (middle tier) for DB inquiries 
and the like.

For the "Main" application use the "Adobe AIR Update Framework."Since all other 
modules are loaded from a single place in the Main application, before I load a 
module I would;Check the date on the local swf file.Check the date on the swf 
file on the application server.If the date on the local file is less than 
(maybe not equal) the date on the application server, download the swf file. If 
possible set the date of the file downloaded = the file date on the application 
server.Run the swf file (module loader).

Before I head down this path, are there any technical reasons why this would 
not work?

Things like the AIR application can't load swf files into the application 
folder, or building the AIR app signs each swf file in such a way that they 
can't be loaded manually would be show stoppers for this approach.

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588

----------------------------------------
From: "Paul Stearns" <pa...@compuace.com.INVALID>
Sent: 6/9/20 5:51 PM
To: "users@flex.apache.org" <users@flex.apache.org>
Subject: Keeping user applications up to date in AIR.
If we deploy applications using AIR we will need to deploy updates. At present 
in the Flash/HTML environment that is easy (except for caching) you put the SWF 
file in the production folder of the website and the next time a user needs the 
module the get the new one.

Our systems consist of one Main.swf file and many modules (independent .swf 
files) which are mostly independent of one another. We would like to have a 
mechanism which would identify new .swf files which need to be loaded to client 
computer whenever the .swf file is needed.

Perhaps if a swf file has been verified for the current session, and the 
current day it would not be checked against the master.

Will "Adobe AIR Update Framework" do this (or help) for our applications? If 
so, where can we get a good introduction tutorial/documentation? If not where 
can we find something which will help accomplish what we are looking to do?

Another alternative is to check if there are updates when the application is 
loaded, but if a change is made to an obscure module which is seldom used by 
few people, we would not want to load it during startup which could/would cause 
the application to load slowly. We prefer JIT deployment.

Paul R. Stearns
Advanced Consulting Enterprises, Inc.

15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016

Voice: (305)623-0360 x107
Fax: (305)623-4588


Reply via email to