Browser Applications

Our methodology when developing applications for use over the internet or an intranet ie using a browser for all screen I/O is to first develop the application and test it in Gensol Client/Server. Then when the modules are correct, the reports are correct, we push the user interface into the Gensol Browser runtime form factor. This involves changing SQL Server Scripts into ASP and it also involves some work to transform the application to fit the browser models that we are able to configure. The outcome is quite stunning, high performing and impressive.

A typical large Gensol application has a figure 8 topology, with the large circle being a client/server network used by motivated, highly trained 5 by 8 people in a typical office environment. The other circle is comprised of a network of internet users gaining access to the same or part of the same database. These users are 7 by 24 and probably haven’t been fully trained to use the software. They may not be as motivated, as computer users, but use the screens to gain access to data they need or to update a small part of the system. These users may need to access the data from different locations in the course of their work. So they form a distributed network of users.

So when we configure an application for use in a Gensol Browser environment we must not only consider the change in the platform form factor but also the typical usage requirements. The Gensol Browser runtime environment has been designed to support these considerations.

Please review the Toolkit notes or a specific application to appreciate the scope of this work. If you have login/password access rights to our on-line Support System, use this to study the various models that we support.