Release 6.0 (dec 1997)
Release 6.1 (nov 1998)
Release 6.2 (sept 1999)
Release 6.3 (nov 2000)
Release 6.4 (nov 2001)
Release 6.5 (nov 2003)

Release 6.0, the first version of Glink for Java, was released at the end of 1997. This release included fully functional ports of Glink's most popular emulation and communications modules, plus a simplified version of the script language.

Release 6.1 was available in late 1998. This version was based on Java 1.1 and this made it possible for the product to reach the local disk and printer, as well as to connect directly to host systems, rather than always via the Web server platform. To secure these features we obtained a certificate from VeriSign. The port of the script language was far more complete. Because of the heavy resource usage of Java 1.1, in particular the 'Swing' GUI package, Release 6.1 was only qualified for the then latest versions of "Internet Explorer" and "Netscape".

Release 6.2 broke significant new ground in September 1999 in that we released three versions of it. The normal applet still used the Swing GUI package, and would only run well under the then latest "Internet Explorer" and "Netscape". An alternative applet used the Java 1.1 AWT (Abstract Windowing Toolkit) GUI package instead of Swing. This ran under any browser that supported Java 1.1, but that version did not allow end-user configuration from the applet. The configuration could only be changed using the administration program. Finally we introduced an application version that could be downloaded and installed locally as a Java desktop application directly under the Java Virtual Machine on the desktop platform. The application version used Swing, but showed none of the resource problems experienced with the applets.

Release 6.3 in November 2000 added yet another variety of the application version: a server-less stand-alone desktop application that doesn't require a Glink for Java server. The configuration is stored on the local file system, and each workstation needs a valid license file in order to operate. In addition, Release 6.3 added a brand new Java API to Glink for Java, allowing programmers to use Glink for Java as a service in integrated applications. The API can be used to tailor and enhance Glink, to add Glink functionality to user-written workstation applications or to add Glink functionality to server-side applications running on Application servers in three tier architectures.

Release 6.4 was introduced in November 2001, based on the Java 2 Runtime Environment. This added enhancements in printing and font management, in addition to preparing the ground for more advanced facilities found in Java 2, such as secure communication. It also brought an optimized version of the Glink API that can be used by application developers needing performance, for example those developing server-side e-business applications supporting hundreds or thousands of simultaneous users needing mainframe application access.
To complement this last feature Release 6.4 introduced Gargen, a Java bean generator that largely automates programming of Java beans that access existing mainframe systems. The beans can be standard beans used by servlets on any Web server, or Enterprise Java Beans for use in applications running on J2EE compliant Application servers. Mainframe connections from Enterprise Java Beans are managed by the G&R J2EE compliant Connector, Gconnect, also introduced in Release 6.4.
To support the high performance demands of server-side applications, we introduced a new communications stack, Direct GCOS Access. DGA is a Java implementation of the G&R/GCOS access protocol that allows direct connection to GCOS systems without passing through a front-end or gateway. Previously only available in our UNIX/NT based Ggate product, this communications stack is proven by independent measurement to be far the most efficient way of accessing GCOS applications.

Release 6.5 was introduced in November 2003 , adding the ability to run Glink in Web mode and also to start Glink using Java Web Start technology. Release 6.5 has support for SSL connections to mainframes with SSL support. Release 6.5 is probably the most advanced Java terminal emulator now available on the market in terms of user interface features, scriptability, available emulations and modes of operation.
Its different modes of operation: applet, Web Start application, workstation application or web server application, make it the ideal terminal emulator for all situations. Its API makes it the perfect product for tailoring emulation usage to the user workstation environment, or adding mainframe application access to user-written workstation applications. The availability of the optimized API to server-side applications make Glink the ideal tool for adding mainframe application access to your e-business applications.
Despite the new look and possibilities introduced in the Java version, you can regard Glink for Java as functionally identical to Glink for Windows because they execute the same emulation and communications logic. Our Java developers have ported the relevant Windows code line-by-line into Java to give you a robust and well proven product in this new environment.