�??xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>&#x56FD;&#x4EA7;&#x4E00;&#x533A;&#x4E8C;&#x533A;&#x68;&#x2C;&#x6B27;&#x7F8E;&#x89C6;&#x9891;&#x514D;&#x8D39;&#x4E00;&#x533A;&#x4E8C;&#x533A;&#x4E09;&#x533A;&#x2C;&#x5929;&#x5802;&#x0430;&#x5728;&#x7EBF;&#x4E2D;&#x6587;&#x5728;&#x7EBF;&#x65E0;&#x9650;&#x770B;&#x63A8;&#x8350;</title><link>http://www.aygfsteel.com/littlebug/category/15279.html</link><description>Simple and Effective</description><language>zh-cn</language><lastBuildDate>Sat, 24 Aug 2013 11:26:17 GMT</lastBuildDate><pubDate>Sat, 24 Aug 2013 11:26:17 GMT</pubDate><ttl>60</ttl><item><title>JDBC3.0 Specification���译�Q�第四章</title><link>http://www.aygfsteel.com/littlebug/archive/2007/05/22/119224.html</link><dc:creator>LittleBug</dc:creator><author>LittleBug</author><pubDate>Tue, 22 May 2007 13:18:00 GMT</pubDate><guid>http://www.aygfsteel.com/littlebug/archive/2007/05/22/119224.html</guid><wfw:comment>http://www.aygfsteel.com/littlebug/comments/119224.html</wfw:comment><comments>http://www.aygfsteel.com/littlebug/archive/2007/05/22/119224.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.aygfsteel.com/littlebug/comments/commentRss/119224.html</wfw:commentRss><trackback:ping>http://www.aygfsteel.com/littlebug/services/trackbacks/119224.html</trackback:ping><description><![CDATA[
<p align="center" style="text-align: center; text-indent: -84pt; margin-left: 84pt;"><strong><span style="font-size: 21pt;">�W�四�?nbsp;&nbsp;&nbsp; 概述</span></strong></p>
<p style="text-indent: 21pt;"><span>JDBC</span><span>应用�E�序接口�?/span><span>Java</span><span>�~�程语言讉K��一个或多个数据源提供了一�U�途径。在大多数情况下�Q�数据源是用</span><span>SQL</span><span>讉K��的关�p�L��据库���理�pȝ��。尽���如此，支持</span><span>JDBC</span><span>技术的驱动�E�序也可以访问其他的数据源，包括遗留文�g�pȝ��</span><span>(legacy file systems)</span><span>和面向对象的�pȝ���?/span><span>JDBC</span><span>应用�E�序接口的一个主要动机就是�ؓ应用�E�序可以讉K���q�泛的数据源提供标准的应用程序接�?/span><span>(API)</span><span>�?/span></p>
<p style="text-indent: 21pt;"><span>�q�一章介�l�了一�?/span><span>JDBC</span><span>应用�E�序接口的关键概��c��除此之外，�q�描�q�C��</span><span>JDBC</span><span>应用�E�序的两�U�运行环境，以及讨论了不同的功能角色在每个运行环境中是怎样被实现的。两层和三层逻辑�l�构能够在大量的物理�l�构上被实现�?/span></p>
<p><span><strong><span style="font-size: 15pt;">4.1建立一个连�?/span></strong></span><span></span><strong><span style="font-size: 15pt;"></span></strong></p>
<p style="text-indent: 21pt;"><span>JDBC</span><span>应用�E�序接口定义�?/span><span>Connection</span><span>接口来表�C�Z��个到潜在数据源的�q�接�?/span></p>
<p style="text-indent: 21pt;"><span>在典型情况下�Q?/span><span>JDBC</span><span>应用�E�序会用两种方式中的一�U�来�q�接到目标数据源�Q?/span></p>
<p style="text-indent: -21pt; margin-left: 57pt;"><span>&#9632;</span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span>DriverManager </span><span>&#8212;&#8212;</span> <span>�q�个被充分实现的�c�d��最初的</span><span>JDBC1.0</span><span>应用�E�序接口中介�l�过�Q�它需要应用程序装载一个特定的驱动�Q�这一驱动使用���编码的�l�一资源定位�?/span><span>(URL)</span><span>�?/span></p>
<p style="text-indent: -21pt; margin-left: 57pt;"><span>&#9632;</span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span>DataSource </span><span>&#8212;&#8212;</span> <span>�q�个接口�?/span><span>JDBC2.0</span><span>可选包应用�E�序接口</span><span>(Optional Package API)</span><span>中介�l�过。与</span><span>DriverManager</span><span>相比它被作�ؓ首选，因�ؓ他允许潜在数据源的细节对应用�E�序透明。一�?/span><span>DataSource</span><span>对象的属性被讄���以后可以表示一个特定的数据源。当它的</span><span>getConnection</span><span>�Ҏ��被调用以后，</span><span>Datasource</span><span>的实例将会返回一个到数据源的�q�接。应用程序可以通过改变</span><span>Datasource</span><span>对象的属性来�q�接��C��同的数据源，而不需要改变应用程序的代码。同��L���Q�一�?/span><span>DataSource</span><span>可以在不改变使用它的应用�E�序的代码的前提下被改变�?/span></p>
<p style="text-indent: 21pt;"><span>JDBC</span><span>应用�E�序接口�q�定义了</span><span>DataSource</span><span>接口的两个重要扩展来支持企业�U�的应用�E�序。这些扩展就是以下的两个接口�Q?/span></p>
<p style="text-indent: -21pt; margin-left: 57pt;"><span>&#9632;</span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span>ConnectionPoolDataSource </span><span>&#8212;&#8212;</span> <span>支持物理�q�接高速缓冲和重用�Q�物理连接改善了应用�E�序的性能和可伸羃性�?/span></p>
<p style="text-indent: -21pt; margin-left: 57pt;"><span>&#9632;<span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span>XADataSource </span><span>&#8212;&#8212;</span> <span>提供了在分布式事务中可共享的�q�接�?/span></p>
<p><span><strong><span style="font-size: 15pt;"></span></strong></span><span><strong><span style="font-size: 15pt;">4.2执行SQL</span></strong></span><span><strong><span style="font-size: 15pt;">表达式以及操作结果集</span></strong></span><span></span><strong><span style="font-size: 15pt;"></span></strong></p>
<p style="text-indent: 21.75pt;"><span>一旦一个连接被建立�Q�那么��用这个连接的应用�E�序���可以用</span><span>JDBC</span><span>应用�E�序接口对目标数据源�q�行查询和更新�?/span><span>JDBC3.0</span><span>应用�E�序接口提供了对大多数实��C���?/span><span>SQL99</span><span>�Ҏ��的支持。因��Z��同的厂商都在不同的��别支持这些特性，�?/span><span>JDBC</span><span>应用�E�序接口则包括了</span><span>DatabaseMetadata</span><span>接口。应用程序能够��用此接口来确定它们��用的数据源是否支持某一�Ҏ���?/span><span>JDBC</span><span>应用�E�序接口�q�定义了转义语法使得应用�E�序可以讉K��非标准的厂商定义的特性。�{义语法的优点是可以���?/span><span>JDBC</span><span>应用�E�序能够像本地应用程序一栯���问相同的�Ҏ��，而同时又能够保证应用�E�序的可�U�L��性�?/span></p>
<p style="text-indent: 21.75pt;"><span>应用�E�序使用</span><span>Connection</span><span>接口中的�Ҏ��来定义事务的属性和创徏</span><span>Statement</span><span>�Q?/span><span>PreparedStatement</span><span>�?/span><span>CallableStatement</span><span>对象。这些表辑ּ�被用来执�?/span><span>SQL</span><span>表达式和���索结果集�?/span><span>ResultSet</span><span>接口���装</span><span>SQL</span><span>的查询结果。表辑ּ�也可以被扚w��执行�Q�即允许应用�E�序向数据源提交多条更新语句作�ؓ执行的单个单元�?/span></p>
<p style="text-indent: 21.75pt;"><span>JDBC</span><span>应用�E�序接口�?/span><span>RowSet</span><span>接口扩展�?/span><span>ResultSet</span><span>接口�Q�从而�ؓ列表数据提供了一个容器，而这��h��标准�l�果集更加通用。一�?/span><span>Rowset</span><span>对象是一�?/span><span>JavaBeans&#8482;</span><span>�l��g�Q�它可以在没有连接到数据源的情况下对它进行操作。例如，一�?/span><span>RowSet</span><span>可以被串行化�Q�因此也可以在网�l�之间被传输�Q�这寚w��些想不需�?/span><span>JDBC</span><span>驱动和数据源�q�接而对表格数据�q�行操作的小型客��L��是非常有用的�?/span><span>RowSet</span><span>的另一个特性是能够包含一个阅��d��来访问�Q意表格�Ş式的数据�Q�而不仅仅是关�p�L��据库中的数据。更�q�一步的�Q�一�?/span><span>RowSet</span><span>对象可以在当它与数据源失去连接的时候更新它的行。它可以包含一个记录器�Q�把那些更新写回到潜在的数据源�?/span></p>
<p><st1:chsdate year="1899" month="12" day="30" islunardate="False" isrocdate="False"><span><strong><span style="font-size: 12pt;">4.2.1<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></strong></span></st1:chsdate><span><strong><span style="font-size: 12pt;">支持</span></strong></span><span><strong><span style="font-size: 12pt;">SQL</span></strong></span><span><strong><span style="font-size: 12pt;">高��数据�c�d��</span></strong></span><span></span><strong><span style="font-size: 12pt;"></span></strong></p>
<p style="text-indent: 21pt;"><span>JDBC</span><span>应用�E�序接口定义了标准的�?/span><span>SQL</span><span>数据�c�d���?/span><span>JDBC</span><span>数据�c�d��的映���。这包括�?/span><span>SQL99</span><span>高��数据�c�d��的支持，诸如</span><span>BLOB</span><span>�Q?/span><span>CLOB</span><span>�Q?/span><span>ARRAY</span><span>�Q?/span><span>REF</span><span>�Q?/span><span>STRUCT</span><span>�?/span><span>DISTINCT</span><span>�?/span><span>JDBC</span><span>驱动也可以�ؓ用户定义�c�d���Q?/span><span>UDTs</span><span>�Q�实��C��个或多个自定义类型映���。在�q�个映射中，用户定义�c�d���Q?/span><span>UDT</span><span>�Q�被映射��C���?/span><span>Java</span><span>�c�M���?/span><span>JDBC3.0</span><span>应用�E�序接口�q�添加了对外部数据管理的支持�Q�例如一个在数据源外部的文�g中的数据�?/span></p>
<p><span><strong><span style="font-size: 15pt;">4.3两层�l�构模型</span></strong></span><span></span><strong><span style="font-size: 15pt;"></span></strong></p>
<p style="text-indent: 21pt;"><span>一个两层结构模型按功能可以被划分�ؓ客户端层和服务器层，见图</span><span>4-1</span><span>�?/span></p>
<div align="center" class="blogimg" small="0"><img width="300" height="278" alt="" src="http://www.aygfsteel.com/images/blogjava_net/littlebug/2.jpg" border="0" /><br /><br /></div>
<p class="blogimg" style="text-align: center; text-indent: 21pt;" small="0"><span>�?/span><span>4-1<span> </span></span><span>两层�l�构模型</span></p>
<p style="text-indent: 21pt;"><span>客户端层包括了应用程序和一个或多个</span><span>JDBC</span><span>驱动�Q�应用程序负责对以下职责�q�行处理�Q?/span></p>
<p style="text-indent: -21pt; margin-left: 57pt;"><span>&#9632;<span></span></span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span>表现层逻辑</span></p>
<p style="text-indent: -21pt; margin-left: 57pt;"><span>&#9632;<span></span></span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span>业务逻辑</span></p>
<p style="text-indent: -21pt; margin-left: 57pt;"><span>&#9632;<span></span></span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span>对多重事务和分布式事务的���理</span></p>
<p style="text-indent: -21pt; margin-left: 57pt;"><span>&#9632;<span></span></span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span>资源���理</span></p>
<p style="text-indent: 21pt;"><span>在这个模型中�Q�应用程序直接与</span><span>JDBC</span><span>驱动交互�Q�包括徏立和���理物理�q�接以及处理潜在的特定的数据源的�l�节。应用程序可以采用特�D�的实现采用不标准的�Ҏ��或性能调整的优炏V�?/span></p>
<p style="text-indent: 21pt;"><span>�q�个模型的一些缺点包括：</span></p>
<p style="text-indent: -21pt; margin-left: 57pt;"><span>&#9632;<span></span></span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span>伴随着基础�l�构和系�l���的功能��得表现层逻辑和业务层逻辑不能分离。这��׃ؓ使用一个好的体�pȝ��构来�~�写可维护性好的��品代码带来了困难�?/span></p>
<p style="text-indent: -21pt; margin-left: 57pt;"><span>&#9632;<span></span></span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; </span><span>因�ؓ采用了特定的数据库实玎ͼ�降低了应用程序的可移植性。而那些要求连接到多个数据库的应用�E�序必须知道不同厂商的数据库之间的差异�?/span></p>
<p style="text-indent: -21pt; margin-left: 57pt;"><span>&#9632;<span></span></span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span>限制了可伸羃性。通常圎ͼ�应用�E�序在结束之前将保持一个或多个到数据库的物理连接，�q�样���限制了它支持�ƈ发应用程序的数量。在�q�个模型中，性能�Q�可伸羃性和可用性受�?/span><span>JDBC</span><span>驱动和相应的数据源的限制。如果一个应用程序采用了多个驱动�Q�它也可能需要知道每�U�驱动和数据源解册���些限制的不同�Ҏ���?/span></p>
<p><span><strong><span style="font-size: 15pt;">4.4三层�l�构模型</span></strong></span><span></span><strong><span style="font-size: 15pt;"></span></strong></p>
<span>
<p style="text-indent: 21pt;"><span>三层模型�l�构��Z��务逻辑和基����l�构引入了中间层服务器，见图</span><span>4-2</span><span>�Q?/span></p>
<p style="text-indent: 21pt;"><br /><span></span></p>
<div align="center" forimg="1"><img width="556" height="422" alt="" src="http://www.aygfsteel.com/images/blogjava_net/littlebug/3.jpg" border="0" /></div>
</span>
<p>&nbsp;</p>
<p style="text-indent: 21pt;"></p>
<p align="center" style="text-align: center; text-indent: 21pt;"><span>�?/span><span>4-2<span> </span></span><span>三层�l�构模型</span></p>
<p style="text-indent: 21pt;"><span>�q�个体系�l�构被设计来��Z��业��的应用程序提高性能�Q�可伸羃性和可用性。三个层的功能分别�ؓ�Q?/span></p>
<p style="text-indent: -42.75pt; margin-left: 84.75pt;"><strong><span style="font-size: 12pt;"><span>1�?span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span></strong><strong><span style="font-size: 12pt;">客户端层</span></strong><strong><span style="font-size: 12pt;"> </span></strong><span>&#8212;&#8212;</span><span> </span><span>为程序和人的交互实现表现层逻辑的一个层�?/span><span>Java</span><span>�E�序�Q�浏览器和掌上电脑（</span><span>PDAs</span><span>�Q�是常见的客��L��实例。客��L��与中间层应用�E�序交互而且不需要包含�Q何与基础�l�构和数据源相关的功能�?/span><span></span></p>
<p style="text-indent: -42.75pt; margin-left: 84.75pt;"><strong><span style="font-size: 12pt;"><span>2�?span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span></strong><strong><span style="font-size: 12pt;">中间层服务器</span></strong><span> </span><span>&#8212;&#8212;</span><span> </span><span>中间层包括：</span><span></span></p>
<p style="text-indent: -21pt; margin-left: 84pt;"><span>&#9632;</span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span>和客��L��以及业务逻辑层交互的<strong>应用�E�序</strong>。如果该应用�E�序能够与数据源交互�Q�和低��的驱动应用程序接口相比，他将更多地处理像</span><span>DataSource</span><span>对象和逻辑�q�接�q�些高��抽象�?/span><span></span></p>
<p style="text-indent: -21pt; margin-left: 84pt;"><span>&#9632;</span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span>为广泛的应用�E�序提供基础�?strong>应用�E�序服务�?/strong>。这包括���理和共享物理连接、事务管理和屏蔽不同</span><span>JDBC</span><span>驱动之间的差异。最后一点��得编写可�U�L��性良好的应用�E�序更加���单�?/span><span>J2EE</span><span>服务器可以实现应用程序服务器�q�一角色。应用程序服务器可以实现被应用程序所使用的高�U�抽象和直接�?/span><span>JDBC</span><span>驱动交互�?/span><strong><span></span></strong></p>
<p style="text-indent: -21pt; margin-left: 84pt;"><span>&#9632;</span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><strong><span>JDBC</span></strong><strong><span>驱动</span></strong><span>提供到潜在数据源的连接。每个驱动程序在它所使用的数据源所支持的特性基���上实现标准的</span><span>JDBC</span><span>应用�E�序接口。驱动层可以屏蔽标准</span><span>SQL99</span><span>语法和数据源所支持的本地语法之间的差异。如果数据源不是一个关�p�L��据库���理�pȝ���Q�那驱动�E�序则��用应用程序服务器实现关系层�?/span><strong><span></span></strong></p>
<p style="text-indent: -42.75pt; margin-left: 84.75pt;"><strong><span style="font-size: 12pt;"><span>3�?span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span></strong><strong><span style="font-size: 12pt;">潜在数据�?/span></strong><strong><span style="font-size: 12pt;"> </span></strong><strong><span style="font-size: 12pt;">&#8212;&#8212;</span></strong><strong><span style="font-size: 12pt;"> </span></strong><span>��x��据驻留层。它包括关系型数据库���理�pȝ���Q�遗留文件系�l�（</span><span>legacy file systems</span><span>�Q�，对象型数据库���理�pȝ���Q�数据仓库，电子表格或者其他�Ş式的数据。唯一的要求就是有相应的支�?/span><span>JDBC</span><span>应用�E�序接口的驱动程序�?/span><span></span></p>
<p><span><strong><span style="font-size: 15pt;">4.5�?/span></strong></span><span><strong><span style="font-size: 15pt;">J2EE</span></strong></span><span><strong><span style="font-size: 15pt;">�q�_��中的</span></strong></span><span><strong><span style="font-size: 15pt;">JDBC</span></strong></span><strong><span style="font-size: 15pt;"></span></strong></p>
<p><span>&nbsp;&nbsp;&nbsp; </span>J2EE<span>�l��g�Q�例�?/span><span>JavaServer&#8482; Pages</span><span>�Q?/span><span>Servlets</span><span>和企业��</span><span>Java Beans&#8482;</span><span>�Q?/span><span>EJB&#8482;</span><span>�Q�组�Ӟ��常常需要���?/span><span>JDBC</span><span>应用�E�序接口来访问关�p�d��数据。当</span><span>J2EE</span><span>�l��g使用�?/span><span>JDBC</span><span>应用�E�序接口以后�Q�那么可以��用相应的容器来管理它们的事务和数据源。这意味着</span><span>J2EE</span><span>�l��g开发�h员可以不直接使用</span><span>JDBC</span><span>应用�E�序接口的事务管理和数据源管理的工具。具体细节请参�?/span><span>J2EE</span><span>�q�_��规范�?/span></p>

 
<img src ="http://www.aygfsteel.com/littlebug/aggbug/119224.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.aygfsteel.com/littlebug/" target="_blank">LittleBug</a> 2007-05-22 21:18 <a href="http://www.aygfsteel.com/littlebug/archive/2007/05/22/119224.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>JDBC3.0 Specification���译�Q�第二章</title><link>http://www.aygfsteel.com/littlebug/archive/2007/05/22/119222.html</link><dc:creator>LittleBug</dc:creator><author>LittleBug</author><pubDate>Tue, 22 May 2007 13:12:00 GMT</pubDate><guid>http://www.aygfsteel.com/littlebug/archive/2007/05/22/119222.html</guid><wfw:comment>http://www.aygfsteel.com/littlebug/comments/119222.html</wfw:comment><comments>http://www.aygfsteel.com/littlebug/archive/2007/05/22/119222.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.aygfsteel.com/littlebug/comments/commentRss/119222.html</wfw:commentRss><trackback:ping>http://www.aygfsteel.com/littlebug/services/trackbacks/119222.html</trackback:ping><description><![CDATA[<div   id="wmqeeuq"   class=cnt>
<p align=center><span></span><span></span><strong><span style="FONT-SIZE: 21pt">�W�二�?目标</span></strong><span><br></span></p>
<p><span>JDBC</span><span>应用�E�序接口是成熟的技术，它早�?/span><span>1997</span><span>�q?/span><span>1</span><span>月就被提出。在它最初发行的时候，</span><span>JDBC</span><span>应用�E�序接口注重于提供一个基本的调用�U�的�?/span><span>SQL</span><span>数据库的接口。�?/span><span>JDBC2.1</span><span>规范�?/span><span>2.0</span><span>可选择包规范则扩展�?/span><span>JDBC</span><span>的范围。这两个规范包括了对更多高��应用�E�序的支持和使用</span><span>JDBC</span><span>应用�E�序接口的应用程序服务器��Z���q�行于它们之上的应用�E�序的性能所要求的新�Ҏ��的支持�?/span></p>
<p><span>JDBC3.0</span><span>规范的��M��目标是补上那些在很少斚w��的功能缺失。以下的清单列出�?/span><span>JDBC</span><span>以及</span><span>JDBC3.0</span><span>所�Ҏ��的目标和设计原理�Q?/span></p>
<p style="MARGIN-LEFT: 18pt; TEXT-INDENT: -18pt"><strong><span style="FONT-SIZE: 12pt"><span>1�?span> </span></span></span></strong><strong><span style="FONT-SIZE: 12pt">适合</span></strong><strong><span style="FONT-SIZE: 12pt">J2EE</span></strong><strong><span style="FONT-SIZE: 12pt">�?/span></strong><strong><span style="FONT-SIZE: 12pt">J2SE</span></strong><strong><span style="FONT-SIZE: 12pt">�q�_��</span></strong><strong><span style="FONT-SIZE: 12pt"></span></strong></p>
<p style="MARGIN-LEFT: 18pt"><span>JDBC</span><span>应用�E�序接口�?/span><span>Java</span><span>�q�_��的组成技术。因此，</span><span>JDBC3.0</span><span>应该�?/span><span>Java2</span><span>企业版和</span><span>Java2</span><span>标准版的��M��方向保持一致�?/span></p>
<p style="MARGIN-LEFT: 18pt; TEXT-INDENT: -18pt"><strong><span style="FONT-SIZE: 12pt"><span>2�?span> </span></span></span></strong><strong><span style="FONT-SIZE: 12pt">�?/span></strong><strong><span style="FONT-SIZE: 12pt">SQL99</span></strong><strong><span style="FONT-SIZE: 12pt">保持一�?/span></strong><strong><span style="FONT-SIZE: 12pt"></span></strong></p>
<p style="MARGIN-LEFT: 18pt"><span>JDBC</span><span>应用�E�序接口提供了从</span><span>Java</span><span>�~�写的应用程序到标准</span><span>SQL</span><span>的编�E�访问。在</span><span>JDBC2.0</span><span>开发的�q�程中，</span><span>SQL99</span><span>规范�q�处在一�U�变化不定的情况下。现�?/span><span>SQL99</span><span>规范是一个公开的标准，它包括了被数据库���理�pȝ��厂商�q�泛支持的以及那些被很少厂商支持的特性�?/span><span>JDBC3.0</span><span>的目标就是实�?/span><span>SQL99</span><span>中那些极可能在将来五�q�里会被�q�泛支持的特性的子集�?/span></p>
<p style="MARGIN-LEFT: 18pt; TEXT-INDENT: -18pt"><strong><span style="FONT-SIZE: 12pt"><span>3�?span> </span></span></span></strong><strong><span style="FONT-SIZE: 12pt">合�ƈ之前版本的规�?/span></strong><strong><span style="FONT-SIZE: 12pt"></span></strong></p>
<p style="MARGIN-LEFT: 18pt"><span>此规范合�q�了之前三版</span><span>JDBC</span><span>规范以提供一份独立的关于</span><span>JDBC</span><span>应用�E�序接口的规范�?/span></p>
<p style="MARGIN-LEFT: 18pt; TEXT-INDENT: -18pt"><strong><span style="FONT-SIZE: 12pt"><span>4�?span> </span></span></span></strong><strong><span style="FONT-SIZE: 12pt">提供厂商中立的对普通特性的讉K��</span></strong><strong><span style="FONT-SIZE: 12pt"></span></strong></p>
<p style="MARGIN-LEFT: 18pt"><span>JDBC</span><span>应用�E�序接口努力实现对被不同厂商普遍支持的特征的高性能的访问。目标是在一定程度上提供本地应用�E�序能完成的对特性的讉K��。因此，</span><span>JDBC</span><span>应用�E�序接口必须���_��全面和灵�z�M����֏�大量的实现方式�?/span></p>
<p style="MARGIN-LEFT: 18pt; TEXT-INDENT: -18pt"><strong><span style="FONT-SIZE: 12pt"><span>5�?span> </span></span></span></strong><strong><span style="FONT-SIZE: 12pt">�l�箋保持�?/span></strong><strong><span style="FONT-SIZE: 12pt">SQL</span></strong><strong><span style="FONT-SIZE: 12pt">的注�?/span></strong><strong><span style="FONT-SIZE: 12pt"></span></strong></p>
<p style="MARGIN-LEFT: 18pt"><span>JDBC</span><span>应用�E�序接口一直注重于�?/span><span>Java</span><span>�~�程语言到关�p�d��数据的访问�?/span><span>JDBC3.0</span><span>������l�注重于�q�一炏V�?/span><span>JDBC3.0</span><span>不排除和其它技术交互，包括</span><span>XML</span><span>�?/span><span>CORBA</span><span>和非关系型数据，但是最主要的目标将仍然是和关系型数据和</span><span>SQL</span><span>交互�?/span></p>
<p style="MARGIN-LEFT: 18pt; TEXT-INDENT: -18pt"><strong><span style="FONT-SIZE: 12pt"><span>6�?span> </span></span></span></strong><strong><span style="FONT-SIZE: 12pt">为工具和更高层的应用�E�序接口提供基础</span></strong><strong><span style="FONT-SIZE: 12pt"></span></strong></p>
<p style="MARGIN-LEFT: 18pt"><span>JDBC</span><span>应用�E�序接口提供标准的应用程序接口来讉K���q�泛的数据源或者保留系�l?/span><span>(Legacy Systems)</span><span>。通过</span><span>JDBC</span><span>应用�E�序接口的抽象，实现方式的不同之处也变得透明了。这使得</span><span>JDBC</span><span>对于那些想生产轻便工具和应用�E�序的厂商来��_��是一个不可多得的目标�q�_���?/span></p>
<p style="MARGIN-LEFT: 18pt"></p>
<p style="MARGIN-LEFT: 18pt"><span>因�ؓ</span><span>JDBC</span><span>是一个从</span><span>Java</span><span>�~�程语言�?/span><span>SQL</span><span>的调用��的接口，所以，</span><span>JDBC</span><span>应用�E�序接口也适合作�ؓ那些�?/span><span>EJB2.0</span><span>容器���理持久�?/span><span>SQLJ</span><span>�Q�注�Q�SQLJ是一个与Java�~�程语言紧密集成的嵌入式SQL版本</span><span style="COLOR: black"></span><span style="COLOR: black"><span></span><span></span></span><span>�Q�这些高�U�程序的基础�?/span></p>
<p style="MARGIN-LEFT: 18pt"><span></span></p>
<p style="MARGIN-LEFT: 18pt; TEXT-INDENT: -18pt"><strong><span style="FONT-SIZE: 12pt"><span>7�?span> </span></span></span></strong><strong><span style="FONT-SIZE: 12pt">保持它的����?/span></strong><strong><span style="FONT-SIZE: 12pt"></span></strong></p>
<p style="MARGIN-LEFT: 18pt"><span>JDBC</span><span>应用�E�序接口被设计�ؓ���单易懂的接口�Q�但是通过它能够编写更复杂的实体。这一目标是通过定义许多����z�，拥有单一功能的方法来代替通过标志参数控制的少量的复杂而拥有多功能的方法来实现的�?/span></p>
<p style="MARGIN-LEFT: 18pt; TEXT-INDENT: -18pt"><strong><span style="FONT-SIZE: 12pt"><span>8�?span> </span></span></span></strong><strong><span style="FONT-SIZE: 12pt">增强可靠性、实用性和灉|���?/span></strong><strong><span style="FONT-SIZE: 12pt"></span></strong></p>
<p style="MARGIN-LEFT: 18pt"><span>可靠性、实用性和灉|��性是</span><span>J2EE</span><span>�?/span><span>J2SE</span><span>�q�_��的主题，也是</span><span>Java</span><span>�q�_��未来的方向�?/span><span>JDBC3.0</span><span>应用�E�序接口通过增强对若�q�领域的支持体现了这些主题，�q�些领域包括资源���理�Q�通过逻辑�q�接重用预处理语句（</span><span>prepared statements</span><span>�Q�以及错误处理�?/span></p>
<p style="MARGIN-LEFT: 18pt; TEXT-INDENT: -18pt"><strong><span style="FONT-SIZE: 12pt"><span>9�?span> </span></span></span></strong><strong><span style="FONT-SIZE: 12pt">保留对现有应用程序和驱动�E�序的向后兼�Ҏ�?/span></strong><strong><span style="FONT-SIZE: 12pt"></span></strong></p>
<p style="MARGIN-LEFT: 18pt"><span>现有的支�?/span><span>JDBC</span><span>技术的驱动和��用这些驱动的应用�E�序在支�?/span><span>JDBC3.0</span><span>�?/span><span>Java</span><span>虚拟��Z��必须能够�l�箋工作。对于那些只使用了先前版本的</span><span>JDBC</span><span>应用�E�序接口的特性，但是没有使用</span><span>JDBC2.0</span><span>反对的特性的应用�E�序�Q�将不需要�Q何改变而正常运行。现有的应用�E�序�U�L���?/span><span>JDBC3.0</span><span>技术上是�g���单的事情�?/span></p>
<p style="MARGIN-LEFT: 18pt; TEXT-INDENT: -18pt"><strong><span style="FONT-SIZE: 12pt"><span>10�?span></span></span></span></strong><strong><span style="FONT-SIZE: 12pt">允许对连接器的向前兼�?/span></strong><strong><span style="FONT-SIZE: 12pt"></span></strong></p>
<p style="MARGIN-LEFT: 18pt"><span>�q�接器的体系�l�构定义了一个标准的�Ҏ��来打包和部��v资源适配器。这使得</span><span>J2EE</span><span>容器可以通过外部资源集成�q�接器的�q�接、事务和安全���理�?/span></p>
<p style="MARGIN-LEFT: 18pt"><span>JDBC3.0</span><span>应用�E�序接口提供了从</span><span>JDBC</span><span>驱动�E�序�U�L��到连接器体系的途径。这使得那些使用</span><span>JDBC</span><span>技术的产品的厂商更多地转移��C��用连接器应用�E�序接口�Q?/span><span>Connector API</span><span>�Q�成为可能。希望这些厂商会在他们现有的数据源工具上写上&#8220;资源���理器封�?#8221;�Q�这栯���些工具就能够在连接器框架中被重用�?/span></p>
<p style="MARGIN-LEFT: 18pt; TEXT-INDENT: -18pt"><strong><span style="FONT-SIZE: 12pt"><span>11�?span> </span></span></span></strong><strong><span style="FONT-SIZE: 12pt">清楚地规定需�?/span></strong><strong><span style="FONT-SIZE: 12pt"></span></strong></p>
<span style="FONT-SIZE: 10.5pt">JDBC</span><span style="FONT-SIZE: 10.5pt">规范的需求应该是明确的和�Ҏ��识别的�?/span><span style="FONT-SIZE: 10.5pt">JDBC3.0</span><span style="FONT-SIZE: 10.5pt">规范�?/span><span style="FONT-SIZE: 10.5pt">Javadoc</span><span style="FONT-SIZE: 10.5pt">文档规定了哪些特性是必需 的，而哪些特性是可选的�?/span></div>
<img src ="http://www.aygfsteel.com/littlebug/aggbug/119222.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.aygfsteel.com/littlebug/" target="_blank">LittleBug</a> 2007-05-22 21:12 <a href="http://www.aygfsteel.com/littlebug/archive/2007/05/22/119222.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item><item><title>JDBC3.0 Specification���译�Q�第一�?/title><link>http://www.aygfsteel.com/littlebug/archive/2007/05/22/119221.html</link><dc:creator>LittleBug</dc:creator><author>LittleBug</author><pubDate>Tue, 22 May 2007 13:10:00 GMT</pubDate><guid>http://www.aygfsteel.com/littlebug/archive/2007/05/22/119221.html</guid><wfw:comment>http://www.aygfsteel.com/littlebug/comments/119221.html</wfw:comment><comments>http://www.aygfsteel.com/littlebug/archive/2007/05/22/119221.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.aygfsteel.com/littlebug/comments/commentRss/119221.html</wfw:commentRss><trackback:ping>http://www.aygfsteel.com/littlebug/services/trackbacks/119221.html</trackback:ping><description><![CDATA[<p style="MARGIN-LEFT: 84pt; TEXT-INDENT: -84pt; TEXT-ALIGN: center" align=center><strong><font size=4><span style="FONT-SIZE: 21pt"><span><span></span></span></span><span style="FONT-SIZE: 21pt">�W�一�?�l�论</span></font></strong><strong><span style="FONT-SIZE: 21pt"></span></strong></p>
<p style="MARGIN-LEFT: 36pt; TEXT-INDENT: -36pt"><strong><span style="FONT-SIZE: 15pt"><span>1.1<span>&nbsp;&nbsp; </span></span></span></strong><strong><span style="FONT-SIZE: 15pt">JDBC</span></strong><strong><span style="FONT-SIZE: 15pt">应用�E�序接口</span></strong><strong><span style="FONT-SIZE: 15pt"></span></strong></p>
<p style="MARGIN-LEFT: 36pt"><span>JDBC&#8482;</span><span>应用�E�序接口提供了从</span><span>Java&#8482;</span><span>�~�程语言�~�程讉K��关系数据的能力。通过使用</span><span>JDBC</span><span>应用�E�序接口�Q?/span><span>Java</span><span>�~�程语言写的应用�E�序能够执行</span><span>SQL</span><span>表达式，���索结果集和把改变传回潜在的数据源�?/span><span>JDBC</span><span>应用�E�序接口�q�可以和在分布式的、异源的环境中的多种数据源进行交互�?/span></p>
<p style="MARGIN-LEFT: 36pt"><span>JDBC</span><span>应用�E�序接口��Z��</span><span>X/Open SQL CLI</span><span>�Q?/span><span>ODBC</span><span>也是建立在此基础上�?/span><span>JDBC</span><span>提供了从</span><span>Java</span><span>�~�程语言�?/span><span>X/Open CLI</span><span>�?/span><span>SQL</span><span>标准定义的抽象和概念的自然、简单的映射�?/span></p>
<p style="MARGIN-LEFT: 36pt"><span>自从</span><span>1997</span><span>�q?/span><span>1</span><span>月被提出�Q?/span><span>JDBC</span><span>应用�E�序接口���p���q�泛接受和实现。它的灵�z�L��考虑��C��大量的实现方式�?/span></p>
<p style="MARGIN-LEFT: 36pt; TEXT-INDENT: -36pt"><strong><span style="FONT-SIZE: 15pt"><span>1.2<span>&nbsp;&nbsp; </span></span></span></strong><strong><span style="FONT-SIZE: 15pt">�q�_��</span></strong><strong><span style="FONT-SIZE: 15pt"></span></strong></p>
<p style="MARGIN-LEFT: 36pt"><span>JDBC</span><span>应用�E�序接口�?/span><span>Java</span><span>�q�_��的一部分�Q?/span><span>Java</span><span>�q�_��包括�?/span><span>Java&#8482;2</span><span>标准版（</span><span>J2SE&#8482;</span><span>�Q�和</span><span>Java2&#8482;</span><span>企业版（</span><span>J2EE&#8482;</span><span>�Q��?/span><span>JDBC3.0</span><span>被分成了两个包：</span><span>java.sql</span><span>�?/span><span>javax.sql</span><span>。这两个包都被包括到�?/span><span>J2SE</span><span>�?/span><span>J2EE</span><span>�q�_��中�?/span></p>
<p style="MARGIN-LEFT: 36pt; TEXT-INDENT: -36pt"><strong><span style="FONT-SIZE: 15pt"><span>1.3<span> </span></span></span></strong><strong><span style="FONT-SIZE: 15pt">目标读�?/span></strong><strong><span style="FONT-SIZE: 15pt"></span></strong></p>
<p style="MARGIN-LEFT: 36pt"><span>此规范主要面向以下几�c�M�品的厂家�Q?/span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> &nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>实现</span><span>JDBC</span><span>应用�E�序接口的驱动程�?/span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>提供驱动层以上的中间层服务的应用�E�序服务�?/span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>使用</span><span>JDBC</span><span>应用�E�序接口提供服务的工��P��如应用程序生成器</span></p>
<p><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span>此规范也打算��Z��下目的服务：</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>在他们的�E�序中���?/span><span>JDBC</span><span>应用�E�序接口的最�l�用��L��一份说明书</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>开发基�?/span><span>JDBC</span><span>应用�E�序接口的其它应用程序接口的�E�序员的一个�v�?/span></p>
<p style="MARGIN-LEFT: 36pt; TEXT-INDENT: -36pt"><strong><span style="FONT-SIZE: 15pt"><span>1.4<span>&nbsp;&nbsp; </span></span></span></strong><strong><span style="FONT-SIZE: 15pt">感谢</span></strong><strong><span style="FONT-SIZE: 15pt"></span></strong></p>
<p style="MARGIN-LEFT: 36pt"><span>作者要感谢以下专家�l�成员，因�ؓ他们为此规范做出了宝�늚�贡献�Q?/span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>ElhamChandler, Informix</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>Stefan Dessloch, IBM</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>John Goodson, Merant</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>Jay Hiremath, Bluestone</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>Viquar Hussain, Inprise</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>Prabha Krishna, Oracle</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>Scott Marlow, Silverstream</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> &nbsp;&nbsp;</span></span></span><span><span><span> &nbsp;&nbsp; </span></span></span><span>Kuldip Pathak, Informix</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>David Schorow, Compaq</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>Yeh-Heng Sheng, Informix</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> &nbsp;&nbsp;</span></span></span><span><span><span> &nbsp;&nbsp; </span></span></span><span>Mark Spotswood, BEA</span></p>
<p style="MARGIN-LEFT: 57pt; TEXT-INDENT: -21pt"><span><span>�?span> </span></span></span><span><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><span>Satish Viswanatham, iPlanet</span></p>
<p><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Maydene Fisher </span><span>曄���很有耐心地把我们写的东西���译成英语�?/span></p>
<p><span><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Jennifer Ball </span><span>也从书写方式转变成�ؓ我们所希望的用图表表示的方式来表达�?/span></p>
<p style="MARGIN-LEFT: 36.75pt; TEXT-INDENT: -36.75pt"><span><span>&nbsp;&nbsp;&nbsp;&nbsp; </span><span>&nbsp;&nbsp;</span>Graham Hamilton, Rick Cattell, Mark Hapner, Seth White</span><span>以及许多其他曄����?/span><span>JDBC</span><span>技术工作的�?/span></p>
<p style="MARGIN-LEFT: 36.75pt; TEXT-INDENT: -36.75pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span>使此规范的出版成为可能�?/span><span></span><span></span></p>
<img src ="http://www.aygfsteel.com/littlebug/aggbug/119221.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.aygfsteel.com/littlebug/" target="_blank">LittleBug</a> 2007-05-22 21:10 <a href="http://www.aygfsteel.com/littlebug/archive/2007/05/22/119221.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item></channel></rss>                                                                                                                                                                                                                 <footer>
<div class="friendship-link">
<a href="http://www.aygfsteel.com/" title="&#29408;&#29408;&#20037;&#20037;&#20122;&#27954;&#27431;&#32654;&#19987;&#21306;&#95;&#20013;&#25991;&#23383;&#24149;&#20122;&#27954;&#32508;&#21512;&#20037;&#20037;&#50;&#48;&#50;&#95;&#22269;&#20135;&#31934;&#21697;&#20122;&#27954;&#31532;&#20116;&#21306;&#22312;&#32447;&#95;&#26085;&#26412;&#20813;&#36153;&#32593;&#31449;&#35270;&#39057;">&#29408;&#29408;&#20037;&#20037;&#20122;&#27954;&#27431;&#32654;&#19987;&#21306;&#95;&#20013;&#25991;&#23383;&#24149;&#20122;&#27954;&#32508;&#21512;&#20037;&#20037;&#50;&#48;&#50;&#95;&#22269;&#20135;&#31934;&#21697;&#20122;&#27954;&#31532;&#20116;&#21306;&#22312;&#32447;&#95;&#26085;&#26412;&#20813;&#36153;&#32593;&#31449;&#35270;&#39057;</a>

</div>

</footer>


��վ֩���ģ�壺
<a href="http://" target="_blank">�ҽ���</a>|
<a href="http://" target="_blank">�����첼��</a>|
<a href="http://" target="_blank">�������</a>|
<a href="http://" target="_blank">��Ϫ��</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">��Ϫ��</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">ǭ����</a>|
<a href="http://" target="_blank">����</a>|
<a href="http://" target="_blank">ʯ����</a>|
<a href="http://" target="_blank">�ն���</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">��Ʊ</a>|
<a href="http://" target="_blank">���</a>|
<a href="http://" target="_blank">��ף</a>|
<a href="http://" target="_blank">¤����</a>|
<a href="http://" target="_blank">ɯ����</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">��Զ��</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">��ʷ</a>|
<a href="http://" target="_blank">��̩��</a>|
<a href="http://" target="_blank">ʯ��ɽ��</a>|
<a href="http://" target="_blank">�ӽ���</a>|
<a href="http://" target="_blank">¡Ң��</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">�ٸ���</a>|
<a href="http://" target="_blank">�°Ͷ�����</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">������</a>|
<a href="http://" target="_blank">��Դ��</a>|
<a href="http://" target="_blank">����</a>|
<a href="http://" target="_blank">��ƽ��</a>|
<script>
(function(){
    var bp = document.createElement('script');
    var curProtocol = window.location.protocol.split(':')[0];
    if (curProtocol === 'https') {
        bp.src = 'https://zz.bdstatic.com/linksubmit/push.js';
    }
    else {
        bp.src = 'http://push.zhanzhang.baidu.com/push.js';
    }
    var s = document.getElementsByTagName("script")[0];
    s.parentNode.insertBefore(bp, s);
})();
</script>
</body>