Network applications

As the Internet matures, new classes of application are emerging. One interesting development is the network deployment of applications previously regarded as in the domain of the desktop. E-mail, office productivity, and scheduling applications are being deployed on servers using the Web as the front end. Users gain from the convenience of ubiquitous access to applications and data from any connected device, and from the removal of the need to install and maintain applications on the desktop.

This trend can only continue: hand held devices, Internet connected TVs, and other consumer electronics are becoming more powerful, popular and connected. Server and bandwidth resources become cheaper by the day. The corresponding loss of control of one's own data, and the potential lack of privacy of such a model do not appear to be a concern to most users, or at least do not appear to outweigh the advantages of such applications.

The Web based application model is also attractive because it drastically reduces the amount of state kept on the clients. As long as the user can access a machine with a Web browser the application and the user's data is available.

But just how secure is the user's data? How redundant is the infrastructure providing that application? How can one Web application inter-operate with another? What if the application is withdrawn? Web based applications are subject to the same business pressures as any other Internet site. Many of them are simply user gathering or loyalty capturing systems, intended to draw users to a larger site and subject them to intense advertising. If they cease to perform that service, there is no contract or obligation for them to continue to provide service, or allow users to migrate data contained in them elsewhere.

Current deployment of equipment shows a marked separation between ``client'' equipment and ``server'' equipment. Servers are reliable, backed up, and act as central storage and synchronisation points. Clients are unreliable, run applications, and are synchronised with or slaved to servers acting as data repositories. Servers are typically fixed installations, and clients are often portable.

The Web based application is an extension of this model, taking the responsibility for application maintainence and data storage off the home or business desktop or portable device, and moving it onto the fixed Internet or intranet server.

Thin client applications work well when the network resources are available, and less well when the application must function when disconnected from the servers or internet. Traditional applications are still used in such situations.