阅读更多

5顶
0踩

编程语言
JDK6u6的内部版本号是1.6.0_06-b02,这次发布主要是修正了一些Bug。原文如下:
网址:http://java.sun.com/javase/6/webnotes/ReleaseNotes.html
Java SE 6u10Beta的发布则与众不同
  官方发文写到:千万不要被它不起眼的名字(即Java SE 6u10Beta,JDK6更新10Beta版本)所愚弄,它是一个与以前更新版本不同的“动物”(呵呵,有点奇怪哦,我觉得译成生命,或者语言)。它推出了比以往的任何java语言的更新,其中包括发布很久的,功能更强的拥有许多新特性的“信封”。
  以往,java更新版本的发布通常是个新闻稿,其中只有第四个版本号( 10个1.6.0_10 )的变化。不像其他的重大发布,更新版本不得添加,删除或改变任何公开的API ,一般来说这种情况限制了更新公告只包含bug修复。6u10同样包含任何新的或改变公共API的-但是,尽管这一限制,我们仍设法挤进了一些令人难以置信的新功能。
  这可是一次特别的更新!
  它针对一下做了改进:
  1、难以检测JREs,特别是Web浏览器
  2、新JREs难以自动安装
  3、下载量太大
  4、Applets和Web程序的不重叠
在以上改进的同时,他又避免了公共API的改变。你不用在等待Java7,我们可以很快得到修正!
  下面的太长了,大家还是自己看吧:)
Java Kernel

--------------------------------------------------------------------------------

The JRE provides many different APIs: Swing, AWT, ImageIO, SQL, CORBA, RMI, math, XML, XSLT, concurrency... too many to name, and each new release adds more. While the variety of APIs makes it easy to write Java software, it's no coincidence that the JRE has been getting steadily bigger over the years (Java 2 Platform, Standard Edition 1.5 was a smaller download due to better compression; the uncompressed JRE was still bigger).



Figure 1: JRE Size in MB



Java Kernel is a new distribution aimed at getting Java software up and running faster. Instead of a full JRE, users download a small installer (the "kernel") which includes the most commonly needed JRE components. Additional components are downloaded as needed, and the JRE will download remaining components in the background and then reassemble itself.



Figure 2: Kernel Size in MB



In the current build, the typical download size for Swing programs and Java applets is on the order of 4-5MB, compared to 14.4MB for the full JRE.


More information about Java Kernel can be found in the 6u10 FAQ.

Next-Generation Java Plug-In

--------------------------------------------------------------------------------

Java SE 6u10 includes a brand-new implementation of the Java Plug-in, which is used by default as long as you are using Firefox 3 or Internet Explorer. The next-generation plug-in runs applets outside of the browser in one or more separate processes. Applets still appear inside of the web browser window as they always have, but this means that it is now possible to use different JRE versions, command-line arguments, and configurations to run different applets. The isolation provided by running the web browser and the JRE -- two very large, very complex pieces of software -- in separate process spaces improves the reliability of both, and gives applets the same flexibility and control over JRE configurations that other Java software has always enjoyed.

Since applets now feature the same powerful JRE selection and configuration that Java Web Start programs do, it was only natural to use the same mechanism for both. The Java Plug-In now supports using Java Network Launching Protocol (JNLP) files to specify applet configuration and startup options. With very little additional work, you can now deploy the same program as both an applet and a Web Start program, and still take advantage of JNLP services such as PersistanceService and FileSaveService.

New Plug-In Advantages:

Improved reliability
Improved JavaScript communication
Per-applet control of JRE command-line arguments
Per-applet control of JRE memory settings, larger maximum heaps
JNLP support
Per-applet JRE version selection
Improved Vista support
Much more information about the new plug-in can be found in the release notes.

Java Deployment Toolkit

--------------------------------------------------------------------------------

The Java Deployment Toolkit makes deploying Java applets or Java Web Start programs a snap. The Deployment Toolkit JavaScript file provides:

Accurate detection of installed JREs
Seamless JRE installation
Complete applet launching (JRE detection and, if necessary, upgrading) in a single line of code
Complete Web Start program launching in a single line of code
The following HTML code is all it takes to ensure that Java 1.6 is installed and then a Java applet is launched:



Nimbus Look and Feel

--------------------------------------------------------------------------------

When the venerable Metal look and feel for Swing first debuted, its main aesthetic competition was the Windows 95 interface. Given the state of graphical user interfaces a decade ago, Metal was an attractive and elegant alternative to the other common interfaces of the time.

The updated Ocean theme in Java SE 5 helped to keep Metal a viable choice up to the present day, but it's time for Swing's cross-platform look and feel to get an overhaul.

Enter the Nimbus Look and Feel. A brand new, modern look and feel based on Synth, Nimbus provides a polished look to applications which choose to use it. And because Nimbus is drawn entirely using Java 2D vector graphics, rather than static bitmaps, it's tiny (only 56KB!) and can be rendered at arbitrary resolutions.



Figure 3: SwingSet3 in Metal





Figure 4: SwingSet3 in Nimbus



For compatibility reasons, Metal is still the default Swing look and feel, but updating applications to use Nimbus couldn't be simpler. It only takes a single line of code:

UIManager.setLookAndFeel("com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel");You can also force Nimbus to be the default look and feel by specifying -Dswing.defaultlaf=com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel. on the command line. A more permanent way to set the property is to add

swing.defaultlaf=com.sun.java.swing.plaf.nimbus.NimbusLookAndFeelto the file <JAVA_HOME>/lib/swing.properties. You will have to create the swing.properties file if it does not already exist.

For further reading about Nimbus, take a look at the Nimbus early access page.

Performance

--------------------------------------------------------------------------------

Sun's JRE has been steadily getting faster over the years, and 6u10 is no exception. Key performance improvements are the introduction of Java Quick Starter, which will substantially improve Java cold start time on most systems, and a new graphics pipeline on Windows.

The new graphics pipeline will use Direct3D to accelerate most common operations, so the powerful 3D graphics card you probably have in your computer will have a use other than playing games. Translucency, gradients, affine transforms, antialiasing, rectangular fills and copies, and various other graphics operations will all be accelerated by 3D graphics cards. And, unlike previous 3D pipelines which were not robust enough to be enabled by default, the new pipeline is rock-solid and used by default in 6u10.

Read more about these features in Chet Haase's blog.

Improved Patching

--------------------------------------------------------------------------------

Java SE 6u10 includes improvements to patch downloading and installation. Of course this won't be visible until 6u11 shows up, but at that point the update will be downloaded by our new download engine, which monitors your network usage and throttles its bandwidth usage back to avoid interfering with your Internet usage.

The new download engine automatically resumes interrupted downloads, and 6u10 uses a new patching algorithm which will significantly reduce the size of future updates. Unlike current JREs, which prompt you as soon as an update becomes available and then make you wait during the download, 6u10 will download the patch in the background and only prompt for your permission to install when the download is already complete.

Deployment Usability

--------------------------------------------------------------------------------

Java Web Start has always supported versioned downloads, and both applets and Web Start have supported the use of Pack200 compression since it first appeared.

However, both of these features required server-side cooperation, which made them inherently difficult to work with. Even though the required servlets were provided and developers merely needed to install them, that unfortunately is not an option with many web hosts and the features were not as widely used as they might have been.

Starting in 6u10, both versioning and pack200 support are available without any special server support. You still have to enable the feature in the JNLP file or applet tag, but this is as easy as adding


But Wait, There's More!

--------------------------------------------------------------------------------

Like any Java update release, there are also a host of bugfixes, performance improvements, and usability improvements -- more than we can cover in any one article. Java SE 6u10 is the biggest update release (no public API changes) of Java software we have ever shipped, and the fact that there are no public API changes doesn't mean that you won't see anything to be excited about.

So what are you waiting for? The Java SE 6u10 beta is available as an early access download right now -- take a look and tell us what you think!


http://java.sun.com/developer/technicalArticles/javase/java6u10/index.html
5
0
评论 共 1 条 请登录后发表评论
1 楼 cuiyi.crazy 2008-04-20 11:12
这个是好事

其加速也是为了确保自己的领导地位 要不就被稀饭了

发表评论

您还没有登录,请您登录后再发表评论

相关推荐

  • 模块卷宗编写规范

    模块开发卷宗规范

  • 软开开发文档汇集(模块开发卷宗、可行性研究报告、测试分析报告等等)

    包含:测试计划.doc、测试分析报告.doc、概要设计说明书.doc、开发进度月报.doc、可行性研究报告(GB8567——88).doc、 模块开发卷宗.doc、软件需求说明书(GB856T——88).doc、数据库设计说明书.doc、文件给制实施规定.doc、 项目开发总结报告(GB8567——88).doc、用户手册(GB8567——88).doc、结构.doc等等...,可用于开发文档参考..

  • 模块开发卷宗(GB8567——88).doc

    模块开发卷宗(GB8567——88).doc模块开发卷宗(GB8567——88).doc模块开发卷宗(GB8567——88).doc模块开发卷宗(GB8567——88).doc模块开发卷宗(GB8567——88).doc模块开发卷宗(GB8567——88).doc模块开发卷宗(GB8567——88).doc模块开发卷宗(GB8567——88).doc

  • [转]软件开发规范—模块开发卷宗(GB8567——88)

    做软件开发是有那么一套国准可参照的,当然就是那些文档了,这里列出一下所有软件开发的规范文档: 操作手册 用户手册 软件质量保证计划 软件需求说明书 概要设计说明书 开发进度月报 测试计划文档 测试分析报告 数据库设计说明书 软件配置管理计划 模块开发卷宗 详细设计说明书 项目开发总结报告 我现在再做的东西是数据库设计说明书,两天前才写玩模块开发卷宗,那时候在网上...

  • 软件文档写作之模块开发卷宗模板.doc

    内容详细介绍了软件文档写作中模块开发卷宗的模板

  • 软件项目模板-模块开发卷宗.zip

    内容真实可靠欢迎随时下载

  • 模块开发卷宗(GB8567——88)

    模块开发卷宗(GB8567——88) 1标题 软件系统名称和标识符 模块名称和标识符(如果本卷宗包含多于一个的模块,则用这组模块的功能标识代替模块名) 程序编制员签名 卷宗的修改文本序号 修改完成日期 卷宗序号(说明本卷宗在整个卷宗中的序号) 编排日期(说明整个卷宗最近的一次编排日期) 2模块开发情况表 3功能说明 扼要说明本模块(或本组模块)的功能,主要是输入、要求的处理、...

  • 软件开发-模块开发卷宗

    扼要说明本模块(或本组模块)的功能,主要是输入、要求的处理、输出。可以从系统设计说明书摘录。同时列出在软件需求说明书中对这些功能的说明的章、条、款。

  • 模块开发卷宗

      (转载自国家计算机标准和文件模板) 1 标题   软件系统名称和标识符   模块名称和标识符(如果本卷宗包含多于一个的模块,则用这组模块的功能标识代替模块名)  程序编制员签名  卷宗的修改文本序号  修改完成日期   卷宗序号(说明本卷宗在整个卷宗中的序号)  编排日期(说明整个卷宗最近的一次编排日期)2 模块开发情况表 3 功能说明   扼要说明本模块(或本组模块)的功能,主要是输入、要求...

  • 7-模块开发卷宗.doc

    文档参考学习使用,适用于相关专业写设计与说明书使用。

  • 模块开发卷宗(GB8567-88)

    模块开发卷宗(GB8567-88)简洁、实用的特性,相信能够为大家利用人力、物力、财力、资源等带来许多帮助...该文档为模块开发卷宗(GB8567-88),是一份很不错的参考资料,具有较高参考价值,感兴趣的可以下载看看

  • 软件工程模块开发卷宗_软件开发陷高成本、低效率怪圈,飞算全自动软件开发平台或可破局...

    随着产业互联网时代的到来,传统企业数字化的需求也爆发式增长,带动了软件开发市场的火爆。数据显示,国内软件开发与服务行业中,员工人数小于 50 人的中小企业数量约占软件开发公司总数的 70%,而这些软件开发企业却普遍面临成本高、效率低、开发周期长等一系列难题。艾瑞数据显示,在国内软件开发行业,2016-2019年研发经费复合增速为14.4%,但是利润总额复合增速只有10.7%。这意味着,企业的研发投...

  • 对模块开发卷宗的理解_【设计思维】&quot;真&quot;模块化根本就不需要读源码!...

      对很多人来,嵌入式软件开发过程中模块化(Modularization)是一个海市蜃楼、是一个书面词汇、是一个过气的时尚——模块化似乎从未真正的实现过。吹牛时人们常不屑的说:没吃过猪肉,但还没看过猪跑么?事实上,如果讨论的对象是嵌入式软件,很多人可能真的没有看过猪跑。在话题变得更像都市传说的之前,我想问一个问题:为什么要模块化?有经验的人会说:为了代码复用(Code Reuse)进一...

  • 模块开发卷宗编写规范

    扼要说明本模块(或本组模块)的功能,主要是输入、要求的处理、输出。可以从系统设计说明书摘录。同时列出在软件需求说明书中对这些功能的说明的章、条、款。

  • 软件工程及其文档汇总

    对待开发系统的一个全面、真实、简略的定义性说明文档。引言1.1 文档的范围和目的1.2 概述1.2.1 目标1.2.2 约束条件功能和数据描述2.1 系统体系结构 (结构环境图 ACD)2.2 ACD 描述说明子系统描述3.1 子系统 N 的体系结构图定义3.1.1 体系结构流程图 AFD3.1.2 系统模块描述3.1.3 性能问题描述3.1.4 设计约束3.1.5 系统构件分配3.2 体系结构字典3.3 结构互连图及其描述。

  • 对模块开发卷宗的理解_软件开发,你必须要知道的8大流程-云智海联

    互联网蓝海经济一直在发展,而我们企业的发展离不开互联网门户,因此很多企业都想在互联网中,用软件来展示企业的优势及服务项目,那么在制作软件中有哪些问题呢,下面就由云智海联为大家讲解一下,在互联网软件发开的中,需要避免的一些问题和正规的项目流程:1、首先制定项目计划,最初计划是里程碑性质的。可以先按瀑布模型设置,里程碑点主要为需求评审、设计评审、经过代码开发和单元测试后进行集成测试、部署上线是一个很重...

  • 对模块开发卷宗的理解_火爆开发概念之——微服务实践篇

    什么是微服务?目前,后端开发比较火爆的概念就是微服务,微服务是软件领域现阶段无人不提的话题,也是未来的一个发展方向。然而,据调查和了解,很多开发者将微服务下的单体应用和SOA(面向服务架构)服务治理下的单体应用混为一谈,认为二者是一样的模式,大量的系统在十几年前都已经是以SOA为基础的分布式系统了,那么微服务作为新的架构标准与SOA有什么差异点呢?其本质区别在于设计原理,微服务是去中心化设计,SO...

Global site tag (gtag.js) - Google Analytics