Client and Server Standards
The paragraphs below describes W3Schools' vision about future Internet
Executables, C++ (and Java too) must die
Neither C++ nor Java can ever create standard components that can run on all
computers. There is no room for these languages in future distributed
applications. Executables are not standard. COM objects are not standard, DLL-files are not standard. Registry settings
are not standard. INI-files are not standard. None of these components must be
allowed to destroy your dream of a standard distributed application that will
run on almost any computer in the world.
Clients must be Standard Internet Browsers
Application clients must be standard clients without any additional
components. No part of the applications must be stored on client computers. The
application must never use, or rely on, any components, dll- or ini-files,
registry settings or any other non standard settings or files stored on the
client computer. (Then you can start calling it a Thin Client). Our best
suggestion is to let all clients use standard Internet browsers like Internet
Explorer, Netscape, or Firefox running on Windows or Mac computers.
Servers must be Standard Internet Servers
Application servers must be standard Internet servers running standard software
without any additional components. The
application must never use, or rely on, any components, dll- or ini-files, registry
settings or any other non standard settings or files stored on the server. Our best suggestion is to use a
standard Internet server like Internet Information Services (IIS), with a standard
request-handler like Active Server Pages (ASP), and a standard database
connector like Active Data Objects (ADO). As your data-store you should use a standard SQL based
database like Oracle or Microsoft's SQL Server.
Applications must use Internet Communication
Application clients and servers must not be allowed to communicate via any proprietary protocol.
Clients must request servers via a standard Internet protocol and servers must respond via
the same protocol. Clients must be able to use any service without having to maintain a permanent
connection to the server. Our best suggestion
is to let servers be requested with standard stateless Internet HTTP requests.
should respond with a standard stateless Internet HTTP response.
|See why there are 20,000+ Ektron integrations worldwide.
Request an INSTANT DEMO or download a FREE TRIAL today.