The presented interface is being developed as a collaborative project between European Bioinformatics Institute (EMBL-EBI), Hinxton, UK (within the Biostandards project in the Industry Support Programme) and German Cancer Research Center (DKFZ), Heidelberg.
Also the implementation is quite different from WPI. The W2H presents a real client-server architecture. A user is a client using the Netscape Navigator (WWW browser) on her/his computer, and all requests are transferred via network (using HTTP protocol) to the server computer where the GCG programs are running and making the analysis. We tried our best to minimize the number of necessary round-trips between client and server.
A typical scenario starts by choosing one or more sequences you want to perform some analysis on. Then you select or type the application you want to run. An application program window appears, displaying the selected sequences as input and allowing you to set the required and optional parameters before running the program. >From the application window the program is started and the result window appears. Either you refresh the window by clicking a button, or you specify the client-pull method to poll a result buffer automatically.
The interface is quite complex covering besides executing the GCG analysis programs also features like sequence selector, search set builder, pattern chooser, access to the sequence databases, uploading client files to the GCG server or showing and manipulating the graphical outputs. Together it consists of more than 30 HTML frames plus, for each application, a specialized form with all mandatory and optional parameters is automatically generated.
For special environments, like workshops, conferences and company intranets, there is a special mode (Intranet mode) which can be easily set up and used without having the UNIX accounts for all users on the server side.
The main advantage of an HTML embedded language is that the whole user request is prepared on the client side without necessity to make the network round-trips. The JavaScript language is capable to verify user's inputs, to suggest the default values and to provide sufficient help. An entering a single value in a form can consequently produce the derived values and let them appear in other places not even in the same form, but also in a quite separate window. It makes the user interface much more powerful and user-friendly.
The W2H design has to take into consideration the security issues even more seriously because it enables an access to the server computer completely, of course only for registered users. The interface considers how to protect the server machine against the unauthorized users and how to protect the user data against a not-allowed access by other users.
Taking advantage of the GCG/WPI configuration files is an important advantage. These .config files contain both parameter definitions and layout description, including dependencies between parameters. They are also supported and quite improved in GCG 9.
Using a platform independent client browser is a general advantage of any WWW interface over other solutions. The W2H depends on using Netscape (because of embedded JavasScript).
Both W2H and www2gcg implements the real client-server architecture which gives the users distributed processing and better relocation of resources.
More independent comparison would be welcome. In the table above, very important features, such as performance, complexity, user learning curve, or maintainability, were not considered at all or only partly.
An another direction, already started, is a design and an implementation of the CORBA-based interface to the the GCG and similar applications.
The W2H interface is provided as a free software (but useful only for
the GCG licensed users) and is available by anonymous ftp at
EBI and
DKFZ