Accessibility

Flex Article

 

Providing Version Synchronization for Deployed Rich Internet Applications


Michael Labriola

Michael Labriola

www.digitalprimates.net

Table of Contents

  1. Introduction
  2. The Situation
  3. A Basic Approach
  4. A More Refined Approach
Comments
Created:
31 Oct 2005
User Level:
Intermediate

As individuals and corporations continue to take advantage of Rich Internet Applications for their ability to engage more customers and attract more business, new projects with larger and more intense requirements are beginning to surface. Most developers would prefer an environment where features and specifications are well documented initially and never change throughout the development cycle. However, the reality of the marketplace dictates that, while a developer should always strive for these ideals, shortened development cycles combined with growing feature sets often result in a staged rollout of new applications, adding new features and fixing unintentional ones as they become identified.

A Rich Internet Application (RIA) developer has limited control over the copies of their application that are executed on a client machine or exist in a browser cache. This can prove particularly problematic when adding a new feature or attempting to fix a problematic bug.

This article stems from my team's recent experience developing a client application with an aggressive schedule, a staged rollout approach, and a requirement for extremely high availability—where it was likely that a user may have the application open for days or weeks without refreshing their browser.

Rich Internet Applications continue to move into traditional application environments and, with this new reach, RIAs can not rely on a user closing or refreshing a web browser to retrieve the latest version. You must keep an RIA that provides functionality to a public kiosk, targets a user desktop, or that provides the interface to a high availability production system up to date or it can quickly become a maintenance nightmare.

In this article, you will develop a simple method and component for dealing with version control and synchronization in deployed client applications.

Requirements

To complete this tutorial you will need to install the following software and files:

Macromedia Flex 1.5

Macromedia ColdFusion MX 7

Tutorials and sample files:

Prerequisite knowledge

  • Familiarity with the basics of assembling a Flex application. If you have none, read Developing Rich Clients with Macromedia Flex by Alistair McLeod and Steven Webster.
  • Familiarity with creating a ColdFusion component and accessing that component from Flex.
  • The ability to set up a ColdFusion data source for the included Microsoft Access database.
Page 1 of 4
Next Page

About the author

Michael Labriola is a Founding Partner and Senior Consultant at Digital Primates, Inc. He has been developing Internet applications since 1995 and has been working with Flex since the 1.0 beta program. Michael worked as an author and technical editor on the Flex 2:Training from the Source book.