📄 ngws_standards.asp@output=print

📁 W3Schools tutorial..web designing
💻 ASP@OUTPUT=PRINT
字号:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-US" xml:lang="en-US" xmlns="http://www.w3.org/1999/xhtml">

<head>
<title>Application Standards</title>
 
<link rel="shortcut icon" href="../favicon.ico" type="image/x-icon" />
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta name="Keywords" content="xml,tutorial,html,dhtml,css,xsl,xhtml,javascript,asp,ado,vbscript,dom,sql,colors,soap,php,authoring,programming,training,learning,beginner's guide,primer,lessons,school,howto,reference,examples,samples,source code,tags,demos,tips,links,FAQ,tag list,forms,frames,color table,w3c,cascading style sheets,active server pages,dynamic html,internet,database,development,Web building,Webmaster,html guide" />

<meta name="Description" content="Free HTML XHTML CSS JavaScript DHTML XML DOM XSL XSLT RSS AJAX ASP ADO PHP SQL tutorials, references, examples for web building." />

<meta http-equiv="pragma" content="no-cache" />
<meta http-equiv="cache-control" content="no-cache" />

<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "../../https@ssl./default.htm" : "../../www./default.htm");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
var pageTracker = _gat._getTracker("UA-3855518-1");
pageTracker._initData();
pageTracker._trackPageview();
</script>

</head>
<body>

<p>From <b>http://www.w3schools.com</b> (Copyright Refsnes Data)</p>

<h1>Client and Server Standards</h1>
<a href="ngws_webservices.asp"><img border="0" src="../images/btn_previous.gif" alt="previous" width="100" height="20" /></a>
<a href="ngws_services.asp"><img border="0" src="../images/btn_next.gif" alt="next" width="100" height="20" /></a>
<hr />
<p class="intro">The paragraphs below describes <b> W3Schools' vision </b>about<b>  </b>future Internet
Distributed Applications.</p>
<hr />
<h2>Executables, C++ (and Java too) must die</h2>
<p>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.&nbsp;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.</p>
<hr />
<h2>Clients must be Standard Internet Browsers</h2>
<p>
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.&nbsp;(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.</p>
<hr />
<h2>Servers must be Standard Internet Servers</h2>
<p>
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.
</p>
<hr />
<h2>Applications must use Internet Communication</h2>
<p>
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.
Servers
should respond with a standard stateless Internet HTTP response.
</p>
<hr />
<a href="ngws_webservices.asp"><img border="0" src="../images/btn_previous.gif" alt="previous" width="100" height="20" /></a>
<a href="ngws_services.asp"><img border="0" src="../images/btn_next.gif" alt="next" width="100" height="20" /></a>

<p>From <b>http://www.w3schools.com</b> (Copyright Refsnes Data)</p>

</body>
</html>
⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -