当前位置: 首页 > 图文教程 > 网络编程 > ASP > javascript asp教程第十三课--include文件

ASP
加密處理使密碼更安全
使用InstallShield制作ASP安装程序(1)
使用InstallShield制作ASP安装程序(2)
使用InstallShield制作ASP安装程序(3)
使用InstallShield制作ASP安装程序(4)
使用InstallShield制作ASP安装程序(5)
使用InstallShield制作ASP安装程序(6)
一个通用数据库显示程序
数据库远程控制的ASP实现
词语搭配游戏的制作(ASP)一
词语搭配游戏的制作(ASP)二
词语搭配游戏的制作(ASP)三
在ASP中使用Oracle数据库
在Web界面下如何生成像资源管理器一样的树形目录(版本2.0)
使用ASP建设私人搜索引擎
用EasyMailObject组件处理Exchange邮件源代码(1)
用EasyMailObject组件处理Exchange邮件源代码(2)
用EasyMailObject组件处理Exchange邮件源代码(3)
用EasyMailObject组件处理Exchange邮件源代码(4)
用EasyMailObject组件处理Exchange邮件源代码(5)

ASP 中的 javascript asp教程第十三课--include文件


出处:互联网   整理: 软晨网(RuanChen.com)   发布: 2009-09-13   浏览: 86 ::
收藏到网摘: n/a

Server Side Includes:

Experienced JavaScript programmers know that code reuse is good. Experienced JavaScript programmers also know that JavaScript functions are data types.

So, we should be able to store a JavaScript function inside a Session Variable or an Application Variable, right? Unfortunately, no. The way to reuse JavaScript functions across many pages is to use SSI: Server Side Includes.

<%@LANGUAGE="JavaScript"%>
<HTML>
<HEAD>
<!--#include file="script13a.asp"-->
<TITLE><% Response.Write( whatTimeIsIt() ) %> </TITLE>
</HEAD>
<BODY>
<%
Response.Write("The date and time are " + DateTime + "<BR><BR>\r")
Response.Write("Tomorrow's date is " + Tomorrow + "<BR><BR>\r")
Response.Write("Tomorrow will be a " + findDayOfWeek(Tomorrow) + "\r")
%>
</BODY>
</HTML>

Click Here to run the script in a new window.

Look at the code for script13.asp. It calls for an include file via this line: <!--#include file="script13a.asp"--> I'll let you see the include file in a moment. But first, I reprinted the client-side code directly below.

<HTML>
<HEAD>
<TITLE>10:57:20 AM </TITLE>
</HEAD>
<BODY>
The date and time are 4/11/2003 10:57:20 AM<BR><BR>
Tomorrow's date is 4/12/2003<BR><BR>
Tomorrow will be a Saturday
</BODY>
</HTML>

The final HTML code looks so nice and simple. You'd never know that the Date() object had been torn down and put back together. Below is the include file.

<%
function whatTimeIsIt()	{	var m=new Date()	var minute=m.getMinutes()	var second=m.getSeconds()	var ampm=false	if (minute >=0 && minute < 10)	{	minute=("0" + minute)	}	if (second >= 0 && second < 10 )	{	second=("0" + second)	}	var hours=m.getHours()	if (hours > 12)	{	ampm=true	hours=hours-12	}	if (hours==12)	{	ampm=true	}	if (hours == 0)	{	hours=hours+12	ampm=false	}	if (ampm)	{	ampm=" pm"	}	else	{	ampm=" am"	}	var myTime=hours + ":" + minute + ":" + second + ampm	return myTime;	}
var DateTime = new Date();
var Month = (DateTime.getMonth() + 1) + "/";
var Day = DateTime.getDate() + "/";
var Year = DateTime.getFullYear();
var DateTime = Month + Day + Year + " " + whatTimeIsIt();
var Tomorrow=new Date()
Tomorrow.setDate(Tomorrow.getDate() + 1)
Month = (Tomorrow.getMonth() + 1) + "/"
Day = Tomorrow.getDate() + "/"
Year = Tomorrow.getFullYear()
Tomorrow = Month + Day + Year
function findDayOfWeek(DateInQuestion)	{	// format for DateInQuestion is mm/dd/yyyy or m/d/yyyy	// and presumes the /'s are present.	myRegExp=/\d{1,2}\//	myMonth=(parseInt(DateInQuestion.match(myRegExp)) -1)	myRegExp=/\/\d{1,2}\//	myDay=new String(DateInQuestion.match(myRegExp))	myDay=parseInt( myDay.substring(1,myDay.length) )	myRegExp=/\/\d{4}/	myYear=new String(DateInQuestion.match(myRegExp))	myYear=parseInt( myYear.substring(1,myYear.length) )	DateInQuestion=new Date(myYear,myMonth,myDay)	DayOfWeek=new Array	DayOfWeek[0]="Sunday"	DayOfWeek[1]="Monday"	DayOfWeek[2]="Tuesday"	DayOfWeek[3]="Wednesday"	DayOfWeek[4]="Thursday"	DayOfWeek[5]="Friday"	DayOfWeek[6]="Saturday"	DayOfWeek=DayOfWeek[DateInQuestion.getDay()]	return DayOfWeek;	}
%>

Imagine that you had 50 pages that all need whatTimeIsIt(), findDayOfWeek(), DateTime, and Tomorrow. You wouldn't want 50 different copies of these functions and variables. No, you would rather have a single copy of these items so that you could manipulate the single copy and execute your updates to all 50 pages at once.

Now you know how to do that.

Moving Forward:

This concludes Section 03. Next up Server and Error objects in Section 04.