
19
G&
GLIN
TM
browser
http
Glink on the application server
Glink API for server side applications
Glink provides you with an API (Application Programming Interface) that is ideally suited for application
development using three-tier architectures. This architecture uses ‘thin’ clients (usually browsers) that only
do presentation. The business logic of the application runs on an Application server. The interface between
the client and the application is an Active Server Page or ASP.NET Web Form page. Glink’s API provides
this new middle-tier business logic with access to vital legacy systems running on mainframes. Using the
functionality of ASP.NET Web Services support, you can even use Glink.GlinkAPI to transform legacy
applications into Web services.
You use the Glink.GlinkAPI .NET component to develop server side applications, launched from Active
Server Pages (ASP) or ASP.NET Web Form (ASPX) pages.
Your server side application needs a Glink Enterprise Edition license to start as many simultaneous sessions
as are licensed. An optimized Glink.GlinkAPI .NET component using much less memory increases the
number of simultaneous sessions that can be supported on production systems. The Glink component can
be a session object belonging to the specific client that launched it, or it can be an application object, shared
by all clients using the same ASP/ASPX.
Note that G&R provide a compatible API with Glink for Java Enterprise Edition. Glink for Java Enterprise
Edition, with the Java version of the API is designed to give the same three-tier architecture development
capability in the cross-platform Java environment. It can be used with any web server that supports Servlets,
and also with full-blown J2EE compatible application servers such as BEA's WebLogic.
IIS
Active
Server
Page
Session
Manager
Glink.
GlinkAPI
Komentáře k této Příručce