Future prospects for Internet distributed applications

Distributed Internet applications for the future ProgramThe prospect of executables, C ++ (and Java) will perish.

In the past, C ++ and Java were unable to create standard components running on all computers. In the future distributed applications, these languages have no room for development. Executables are non-standard. COM objects are also non-standard, and DLL files are non-standard. Registry settings is non-standard, and the INI file is non-standard. We will not let these components destroy the dream of a standard distributed application, which can run on all the computers in the world.

The client must be a standard Internet browser

The application client must be a standard client without additional components. No part of the application can be stored on the client computer. Applications cannot use or rely on any components, DLL or INI files, registration settings, or any other non-standard settings or files stored on client computers. (This is called a thin client ). It is recommended that all users use standard Internet browsers, such as Internet Explorer, Netscape, or Firefox, on Windows or Mac.

The server must be a standard Internet server.

The application server must be a standard Internet server that runs standard software without additional components. Applications cannot use or rely on any components, DLL or INI files, registration settings, or any other non-standard settings or files stored on client computers. We recommend that you use standard Internet servers, such as IIS, standard request processing programs, such as ASP, and standard database connection programs (interfaces), such as ADO. As for data storage, standard SQL-based databases should be used, such as oracle or ms SQL Server.

Applications must communicate over the Internet

Application clients and servers are not allowed to communicate through any private protocol. The client must request the server through the standard Internet protocol, and the server must respond through the same protocol. The client must be able to use any service without having to maintain a permanent server connection. We recommend that you make requests to servers using standard HTTP requests without borders. Servers should use standard, borderless Internet HTTP responses for responses.