How GO-Global 6 Works
With GO-Global, users access Windows applications the same way they access web sites and web applications: by clicking a link. When a user clicks a link to a Windows application that has been published via GO-Global, the application opens exactly as specified.
Administrators can specify whether the application fills the browser window or displays inside the browser alongside other content. Administrators can also direct the application to load a specific document or display a specific image or form when the user clicks the application link.
If the GO-Global App is installed on the client device, the application can access local files and devices, and can run outside the browser window as if it were running locally.
And if the application’s manufacturer has leveraged GO-Global’s SDKs, the application running on the host computer may remotely control web-based content and applications that are running alongside the GO-Global Web App in the browser on the client computer. Alternatively, the application and its GO-Global session may be controlled via GO-Global’s RESTful Web API.
When a user clicks a GO-Global link, the user’s browser connects to a Web server and runs the GO-Global Web App. The GO-Global Web App then opens a WebSocket connection to the Application Publishing Service (APS) on the host, and the APS creates a session for the user.
To create the session, the APS calls the GO-Global System Extensions Driver (GGSE), which loads the Win32 subsystem, the GO-Global Virtual Display Driver, and the other session-specific drivers. The APS then starts the session’s Logon.exe process and the application specified in the link.
When the Logon.exe process and other applications running in a GO-Global session call operating system modules (e.g., GDI32, User32) to create windows or draw to the display, GO-Global directs the calls to the session’s instance of the Win32 subsystem. The Win32 subsystem then sends graphics commands to the GO-Global Virtual Display Driver, which converts the graphics commands to GraphOn’s RapidX Protocol (RXP) requests and queues the requests to be sent to the GO-Global Web App.
Finally, the GO-Global Display Server, which runs in the session’s Logon.exe process, sends the RXP requests to the Web App via the APS, and the Web App executes the RXP commands and displays the session’s applications in the browser.
GO-Global does not use Remote Desktop Services
GO-Global is the only product that enables multi-user remote access to Windows applications without using either Microsoft Remote Desktop Services, or the multi-session functionality that is built into Windows. Unlike products that extend Microsoft’s technologies or disable Microsoft’s constraints on its Remote Desktop functionality, GO-Global provides full replacements for Microsoft’s multi-session functionality and its Remote Desktop clients, display driver, and protocol.
For example, in place of Microsoft’s multi-session functionality, the GO-Global System Extensions Driver provides a session-private sandbox for a GO-Global session’s drivers and processes.
In place of Microsoft’s Remote Desktop clients, the GO-Global Web App provides zero-install, browser-based access to remote Windows applications, and the GO-Global App enables remote applications to run as if they were running locally on the client device.
And in place of Remote Desktop’s display driver that converts Windows graphics command to Microsoft’s Remote Desktop Protocol (RDP), the GO-Global Virtual Display Driver converts Windows graphics commands to GraphOn’s RapidX Protocol (RXP), providing efficient and responsive remote access to Windows applications.
GO-Global technology includes extensions and enhancements to the Windows operating system that were developed by some of the best Windows internals experts in the world, as well as 20 years of refinement to GO-Global’s graphics engine and graphics protocol, which were developed by early leaders in Windows graphics applications and application remote access.