ASP.NET

ASP.NET 学习二 内容摘自msdn收藏 How to: Determine How ASP.NET Web Pages Were Invoked

The following table lists ways in which a page can be invoked and the
corresponding Page property values.

Invocation method

Property values

Original request

・ IsPostBack is set to false.

・ PreviousPage is set to null (Nothing in Visual Basic).

・ IsCallback is set to false.

Postback

・ IsPostBack is set to true.

・ PreviousPage is set to null (Nothing in Visual Basic).

・ IsCallback is set to false.

Cross-page posting

・ IsPostBack is set to false.

・ PreviousPage references the source page.

・ IsCrossPagePostBack is set to true.

・ IsCallback is set to false.

Server transfer

・ IsPostBack is set to false.

・ PreviousPage references the source page.

・ IsCrossPagePostBack that is referenced in the PreviousPage is set to false.

・ IsCallback is set to false.

Callback

・ IsPostBack is set to false.

・ PreviousPage is set to null (Nothing in Visual Basic).

・ IsCallback is set to true.

ASP.NET

ASP.NET 学习一 基础 内容摘自msdn

ASP.NET Web pages allow you to create dynamic content for your Web site. With
a static HTML page (.htm or .html file), the server fulfills a Web request by
reading the file and sending it as-is to the browser. In contrast, when
someone requests an ASP.NET Web page (.aspx file), the page runs as a program
on the Web server. While the page is running, it can perform any task that
your Web site requires, including calculating values, reading or writing
database information, or calling other programs. As its output, the page
dynamically produces markup (elements in HTML or another markup language) and
sends this dynamic output to the browser.

Postbacks and Round Trips

ASP.NET pages run as code on the server. Therefore, for the page to be
processed, the page is configured to submit to the server when users click
buttons (or optionally, when users select check boxes or interact with other
controls in the page). Each time, the page is submitted back to itself so it
can run its server code again and then render a new version of itself back to
the user.

The processing cycle for an ASP.NET Web page is this:

1. The user requests the page. (The page is requested using an HTTP GET
method.) The page runs for the first time, performing preliminary processing
if you have programmed it to do so.

2. The page dynamically renders markup to the browser, which the user sees
as a Web page similar to any other page.

3. The user types information or selects from available choices and then
clicks a button. (If users click a link instead of a button, the page might
simply navigate to another page, and no further processing takes place on the
first page.)

4. The page is posted to the Web server. (The browser performs an HTTP
POST method, which in ASP.NET is referred to as a postback .)
Specifically, the page is posted back to itself. For example, if the user is
working with the page Default.aspx, clicking a button on the page posts the
page back to the server with a target of Default.aspx.

5. On the Web server, the page runs again. The information that the user
typed or selected is available to the page.

6. The page performs the processing that you have programmed it to do.

7. The page renders itself back to the browser.

This cycle continues as long as the user is working in the page. Each time the
user clicks a button, the information in the page is posted to the Web server
and the page runs again. Each cycle is referred to as a round trip . Because
page processing occurs on the Web server, each action that the page can do
requires a round trip to the server.

Note An ASP.NET Web page can run client script, which does not require a
round trip to the server, and which is useful for user input validation and
for some types of UI programming.

Java

CodeCoverage的使用方法

1.安装Borland Optimizeit Enterprise Suite 6.0套件，然后注册；
2.打开Code Coverage工具，进行设置，见下图：

3.点击Start now，开始运行applet；
4.进行完操作后，回到Code Coverage,可以查看结果。

文化

对《货币战争》一书的小小结

如有不正确的地方，还请指正！

首先要取得一个国家的货币发行权，不惜一切手段；取得货币发行权后就可以更加方便使用
部分储备金制度(就是通过贷款来获利)、货币与国债死锁的手段来发财致富；
但是由于金本位的原因，黄金和白银增加缓慢，以上两种手段获得的财富
不足以满足银行家们日渐膨胀的胃口，所有出现了法定货币；
有了法定货币后，银行家们就可以使用通货膨胀，通货紧缩来“剪羊毛”了。

金本位:
http://baike.baidu.com/view/249511.htm

部分储备金制度（Fractional Reserve）:
http://zhidao.baidu.com/question/70338222.html
http://en.wikipedia.org/wiki/Fractional-reserve_banking

英格兰银行模式（货币与国债死锁的手段）
http://zhidao.baidu.com/question/47863169.html

通货膨胀:
http://baike.baidu.com/view/4017.htm#8

通货紧缩:
http://baike.baidu.com/view/34349.htm

银根:
http://baike.baidu.com/view/24269.htm

（打仗就要花钱，越大的战争花钱越多，这是尽人皆知的道理。问题是，谁花谁的钱
？由于欧美政府没有货币发行权，政府必须也只能向银行家借钱。战争使物资消耗
达到燃烧般的速度，战争使交战国砸锅卖铁也要坚持，战争使不惜一切代价的政府
不计条件地向银行家融资，难怪战争始终是银行家的最爱。他们策划战争，他们挑
动战争，他们资助战争，国际银行家们华丽的大厦，从来就是建立在死亡枕籍的废
墟之上。

国际银行家另一个赚大钱的手段就是制造经济衰退。首先是扩大信贷，将泡沫吹起
来，等人民的财富大量投入投机狂潮后，然后猛抽银根，制造经济衰退与资产暴跌
。当优质资产价格暴跌到正常价格的十分之一甚至百分之一时，他们再出手以超级
低廉的价格收购，这在国际银行家们的术语中叫做“剪羊毛”。当私有中央银行成立
后，“剪羊毛”行动的力度和范围都达到了史无前例的程度。

最近的一次“剪羊毛”行动，发生在1997年的亚洲“小龙”和“小虎”们身上。中国这
只大肥羊最终能否避免被“剪羊毛”的厄运，就要看中国是否认真去研究发生在历
史上的一幕幕触目惊心的“剪羊毛”惨剧了。

整个过程形象地说就像银行家在鱼塘里养鱼，当银行家向鱼塘里放水时就是在放
松银根，向经济体大量注入货币，在得到大量的金钱之后，各行各业的人就开始在
金钱的诱惑之下日夜苦干，努力创造财富，这个过程就像水塘里的鱼儿使劲吸收各
种养分，越长越肥。当银行家看到收获的时机成熟时，就会突然收紧银根，从鱼塘
中开始抽水，这时鱼塘里的多数鱼儿就只有绝望地等着被捕获的命运。

但是，什么时候开始抽水捞鱼却只有几个最大的银行寡头知道，当一个国家建立了
私有的中央银行制度以后，银行寡头对放水抽水的控制就更加得心应手，收获也就
越加精确。经济发展与衰退，财富积累与蒸发都成为银行家“科学饲养”的必然结果。）

人们手里的钱多了，相对来说商品就少了，所以物价会上涨；
人们手里的钱少了，购买力下降，同时相对来说商品就多了，影响物价之下跌；

Java

64位的jre和32位的jre

下面一段话是从sun的官网上得到的：
There are no 64-bit versions of the Java Plugin, Java Web Start or Java
Control Panel; however the 32-bit versions of the JRE can be installed on
64-bit systems in order to obtain this functionality. Note that only 32-bit
browsers are supported at this time.

首先说明了64位的jre没有java plugin来和浏览器关联，所以就算在64位的机器上安装了64位的jre，
也运行不了applet；但是可以运行用java写的application；但是需要注意的一点是java是向后兼容的；

它又说在64位的系统上可以安装32位的jre来运行applet等程序，但是我试验了半天，只有
j2sdk-1_4_2_12-windows-i586-p可以在64位的机器上安装，其他的比之更高版本根本就安装不上，
安装完成后，进行更新也不行，所以如果要在64位的系统上运行32位的applet的话，必须要使用
32位的浏览器(64位的系统中一般有两个IE，一个32位的，一个64位的)，32位的1.4的jre(当然还要有html文件的配合)；

注释：
1.32位的class文件，可以在64位的jre下正常运行；(不管是applet还是applications都可以运行)
2.以上结论是我在windows 2003的64位系统上测试得出的，其他的环境就不知道了。