If you want users to be able to launch remote applications from their local machine independently of the World Wide Web, you can use Acucorp's remote application server, AcuConnect, to accomplish your goal.
With AcuConnect, users or programs on client machines can launch applications on server machines, whether those servers are part of a local area network, wide area network, or global Internet. (Remember -- the Internet is simply a large TCP/IP network.) While some portions of your application continue to run on the client (e.g., the user interface, interactive programs, etc.), the resource intensive portion runs where it is most efficient . . . on the server.
Should users decide to run their programs on server1 one day and server2 the next, they can do so without making any changes to the application code. They can even run the application locally if they choose.
AcuConnect also provides users access to remote Vision data. If the data is on the same remote server as AcuConnect, no special software is required. If the data is on a third data server, AcuConnect works in tandem with Acucorp's remote file server, AcuServer, to provide seamless data access. AcuConnect can also work with Acu4GL, Acucorp's COBOL-to-RDBMS bridge, to provide seamless access to relational data wherever it resides.
The following figures show AcuConnect in a standard client/server configuration and an Internet configuration. Notice that there is no difference between the two -- Internet deployment via AcuConnect does not require any special knowledge or tools.
Standard client/server configuration
AcuConnect on the Internet: Option 4
To use AcuConnect on the Internet or otherwise, you must prepare your application and define remote application paths.