java英文参考文献.docx

精选优质文档-倾情为你奉上java英文参考文献篇一：外文参考文献译文及原文 本科毕业设计（论文） 外文参考文献译文及原文学 院_计算机学院_ 专 业_计算机科学与技术_ 年级班别_2009级（1）班_ 学 号 学生姓名_ _ 指导教师_ _ 2013年5月目 录 译文： 前言 . 1 第一章微软.NET平台的介绍 . 3 1.1 简介 . 3 1.1.1 .NET平台简介 . 3 1.1.2 微软的.NET和WINDOWS的基因. 4 1.1.3 微软 .NET体系结构 . 4 1.1.4 .NET平台的特点 . 4 1.1.5 多国语言的发展 . 5 1.1.6 平台和处理器独立性 . 6 1.1.7 自动内存管理 . 7 1.1.8 支持的版本 . 7 1.1.9 支持的开放标准 . 8 1.1.10 配置简单 . 8 1.1.11 分布式体系结构 . 9 1.1.12 与非托管代码的互用 . 9 原文： Foreword . 11 Chapter1 Introduction of the Microsoft .NET Platform . 13 1.1 Introduction . 13 1.1.1 Introduction of the .NET Platform . 13 1.1.2 Microsoft .NET and Windows DNA . 15 1.1.3 Microsoft .NET Architecture Hierarchy . 15 1.1.4 Features of the .NET Platform . 16 1.1.5 Multilanguage Development . 17 1.1.6 Platform and Processor Independence . 18 1.1.7 Automatic Memory Management . 19 1.1.8 Versioning Support . 20 1.1.9 Support for Open Standards . 21 1.1.10 Easy Deployment . 22 1.1.11 Distributed Architecture . 23 1.1.12 Interoperability with Unmanaged Code . 23 译文： 前言 在电脑软件的历史上，很少有一种技术能够得到开发者和业界如此强烈的正面响应。全球已经有数百万的开发者下载了Microsoft的.NET软件开发工具包，已经出现了很多有关.NET平台及其相关技术和语言的教材、网站和新闻团体。 Microsoft在创建.NET上已经投入了数十亿美元进行了多年的研究。.NET是一种全面的策略，它由操作系统、数据库服务器、应用程序服务器和.NET运行时库组成，还包括运行于.NET平台之上的操纵语言。 很多人把.NET平台看作先前所说的Windows DNA的实际实现，也有人把它看作是改进先前技术和语言的结果。然而，这些仅仅说明了.NET是对Microsoft以前技术的重大改进。其实.NET平台是从头开始设计的，包括许多内在目标，如安全性、可升级性、可靠性、灵活性和互操作性。为了使.NET平台适合于企业和开发者，所有这些目标从一开始就被考虑到了。 NET平台呈现了Microsoft思想的重大转变。建立.NET平台时，Microsoft表现出对开放标准极大的支持，如XML、SOAP和UDDI，而不是建立自己的标准和技术。而且.NET平台的核心部分（Common Language Infrastructure, CLI）和C#规范都已提交给ECMA，并通过了标准化。 C#来源于C和C+，是一种简单的、现代的、面向对象和类型安全的编程语言，由Microsoft的Anders Hejlsberg专门为.NET平台开发的语言，继承了许多语言的特征，如C、C+和Java。C#是为了综合Visual Basic的简单和C+作为面向对象语言的功能强大的优点而写的，对于开发者来说，C#使企业应用程序的创建、调试和配置变得很容易。有人预言，C#将成为在.NET平台上开发应用程序最受欢迎的语言。 作为Visual Studio IDE的下一个版本，Visual Studio.NET也是.NET战略的关键组成部分。Visual Studio.NET IDE也已经被整合并装入了大量的新功能。位图编辑器、调试器、Web窗体设计器、Windows窗体设计器、Web服务设计器、XML编辑器、HTML编辑器、Web浏览器、服务器资源管理器和多语言支持，所有这些都被集成在IDE中。C#.NET Web开发指导的重点不是教你C#语言的核心内容，而是提供代码实例来帮 1 篇二：Java项目ssh2相关参考文献 Java开发相关参考中英文文献期刊 1Bruce Eckel. Thinking in JavaM. Upper Saddle River, New Jersey, USA:Prentice Hall, 2006 2 陈道鑫,宋绍云,袁中旺,等. ExtJS框架在Web软件开发中的应用J. 电脑知 识与技 术 2011, 07(9): 2044-2047 3 林信良. Spring2.0技术手册M. 北京：电子工业出版社，2005 4 （美）威尔德，斯尼德等著，赵利通译. SpringFramework 2入门经典M. 北 京：清 华大学出版社，2009 5 林寒超,张南平. Hibernate技术的研究J.计算机技术与发展,2006, 16(11): 112-113,116 6 田珂，谢世波，方马.J2EE数据持久层的解决方案J.计算机工程，2003,29(22): 93-95 7 谭怀远. 让Oracle跑得更快:Oracle 10g性能分析与优化思路M. 北京：电子 工业出版社，2011 8 RFC2256: A Summary of the X.500(96) User Schaema for user with LADPv3 J/OL 9王倩宜, 李润娥, 李庭晏. 统一用户管理和身份认证服务的设计与实现J.实验技 术与管理 2004,30(3):236239 10李席广. 基于LDAP的统一身份认证管理系统的设计与实现J. 科技信息 (学术研 究) , 2007,(19): 99-101 11 刘京华.Java Web整合开发王者归来M. 北京：清华大学出版社，2010 12刘春晓,孟祥福,李昕.基于Jboss的数据库连接池研究与实现J. 微处理机: 2008, 29(1): 86-88 13 Craig Walls, Ryan BreidenBach. Spring In ActionM. Manning Publications.2006 14张孝祥. 深入Java Web开发内幕核心基础M. 北京：电子工业出版社.2006 15 Joshua Bloch. Effective JavaM. Piscataway, N.J:IEEE Press, 2009 16李安渝. Web Services技术与实现M. 北京：国防工业出版社，2003 17 李华明. Android游戏编程之从零开始M. 北京：清华大学出版社，2011 18 姚昱旻，刘卫国. Android的架构与应用开发研究J. 计算机系统应用，2008， 17(11)：110-112 19 (美)埃布尔森，(美)柯林斯，(美)森. Google Android揭秘M. 北京：人民邮 电出版社，2010 20 Enck, William, Ongtang, Machigar, McDaniel, Patrick.Understanding Android SecurityJ.IEEE security & privacy, 2009, 7(1): 50-57 21 (美)阿诺德，Ken Arnold，等.Java程序设计语言M.北京：人民邮电出版社， 2006 22 孙卫琴，李洪成.Tomcat 与 Java Web 开发技术详解M.电子工业出版社， 2003.6:1-205 23 SIMSON GARFINKEL.Android CallingJ.Technology Review, 2008, 111(2): 80-99 24 吴亚锋，苏亚光.Android 2.0游戏开发实战宝典M.北京：人民邮电出版社， 2010 25 郭爱芳. 传感器原理及应用M. 西安：西安电子科技大学出版社，2007 26 韩兵. 触摸屏技术及应用M. 北京：化学工业出版社，2008 27 Reto Meier. Professional Android 2 Application DevelopmentM. Birmingham, UK: Wrox, 2010 28 杨丰盛. Android技术内幕.系统卷M. 北京：机械工业出版社，2011 29 王保国. 空气动力学基础M. 北京：国防工业出版社，2009 30 Hohzaki R, Maehara H. A single-shot game of multi-period inspectionJ.European Journal of Operational Research, 2010, 207(3): 1410-1418 31周国烛. 手机游戏从创意到设计M. 北京：国防工业出版社，2008 32BruceEckel.Java编程思想M. 机械工业出版社，2003.10:1-378 33FLANAGAN.Java技术手册M. 中国电力出版社，2002.6:1-465 34孙一林，彭波.Java数据库编程实例M. 清华大学出版社，2002.8:30-210 35LEE ANNE PHILLIPS.巧学活用HTML4M.电子工业出版社，2004.8:1-319 36飞思科技产品研发中心.JAVA应用开发详解M.电子工业出版社， 2003.9:32-300 37耿祥义,张跃平.JAVA实用教程M. 清华大学出版社，2003.5.1:1-354 38孙涌.现代软件工程M.北京希望电子出版社，2003.8:1-246 39萨师煊，王珊.数据库系统概论M.高等教育出版社，2002.2:3460 40Brown.JAVA编程指南（第二版）M. 电子工业出版社，2003.3:1-268 41清宏计算机工作室.JAVA编程技巧M. 机械工业出版社，2004.5:1-410 42朱红,司光亚.JAVA Web编程指南M.电子工业出版社，2001.9:34-307 43赛奎春.JAVA工程应用与项目实践M. 机械工业出版社，2002.8:23-294 篇三：JAVA外文文献+翻译 Java and the Internet If Java is, in fact, yet another computer programming language, you may question why it is so important and why it is being promoted as a revolutionary step in computer programming. The answer isnt immediately obvious if youre coming from a traditional programming perspective. Although Java is very useful for solving traditional stand-alone programming problems, it is also important because it will solve programming problems on the World Wide Web. 1. Client-side programming The Webs initial server-browser design provided for interactive content, but the interactivity was completely provided by the server. The server produced static pages for the client browser, which would simply interpret and display them. Basic HTML contains simple mechanisms for data gathering: text-entry boxes, check boxes, radio boxes, lists and drop-down lists, as well as a button that can only be programmed to reset the data on the form or “submit” the data on the form back to the server. This submission passes through the Common Gateway Interface (CGI) provided on all Web servers. The text within the submission tells CGI what to do with it. The most common action is to run a program located on the server in a directory thats typically called “cgi-bin.” (If you watch the address window at the top of your browser when you push a button on a Web page, you can sometimes see “cgi-bin” within all the gobbledygook there.) These programs can be written in most languages. Perl is a common choice because it is designed for text manipulation and is interpreted, so it can be installed on any server regardless of processor or operating system. Many powerful Web sites today are built strictly on CGI, and you can in fact do nearly anything with it. However, Web sites built on CGI programs can rapidly become overly complicated to maintain, and there is also the problem of response time. The response of a CGI program depends on how much data must be sent, as well as the load on both the server and the Internet. (On top of this, starting a CGI program tends to be slow.) The initial designers of the Web did not foresee how rapidly this bandwidth would be exhausted for the kinds of applications people developed. For example, any sort of dynamic graphing is nearly impossible to perform with consistency because a GIF file must be created and moved from the server to the client for each version of the graph. And youve no doubt had direct experience with something as simple as validating the data on an input form. You press the submit button on a page; the data is shipped back to the server; the server starts a CGI program that discovers an error, formats an HTML page informing you of the error, and then sends the page back to you; you must then back up a page and try again. Not only is this slow, its inelegant. The solution is client-side programming. Most machines that run Web browsers are powerful engines capable of doing vast work, and with the original static HTML approach they are sitting there, just idly waiting for the server to dish up the next page. Client-side programming means that the Web browser is harnessed to do whatever work it can, and the result for the user is a much speedier and more interactive experience at your Web site. The problem with discussions of client-side programming is that they arent very different from discussions of programming in general. The parameters are almost the same, but the platform is different: a Web browser is like a limited operating system. In the end, you must still program, and this accounts for the dizzying array of problems and solutions produced by client-side programming. The rest of this section provides an overview of the issues and approaches in client-side programming. 2.Plug-ins One of the most significant steps forward in client-side programming is the development of the plug-in. This is a way for a programmer to add new functionality to the browser by downloading a piece of code that plugs itself into the appropriate spot in the browser. It tells the browser “from now on you can perform this new activity.” (You need to download the plug-in only once.) Some fast and powerful behavior is added to browsers via plug-ins, but writing a plug-in is not a trivial task, and isnt something youd want to do as part of the process of building a particular site. The value of the plug-in for client-side programming is that it allows an expert programmer to develop a new language and add that language to a browser without the permission of the browser manufacturer. Thus, plug-ins provide a “back door” that allows the creation of new client-side programming languages (although not all languages are implemented as plug-ins). 3.Scripting languages Plug-ins resulted in an explosion of scripting languages. With a scripting language you embed the source code for your client-side program directly into the HTML page, and the plug-in that interprets that language is automatically activated while the HTML page is being displayed. Scripting languages tend to be reasonably easy to understand and, because they are simply text that is part of an HTML page, they load very quickly as part of the single server hit required to procure that page. The trade-off is that your code is exposed for everyone to see (and steal). Generally, however, you arent doing amazingly sophisticated things with scripting languages so this is not too much of a hardship. This points out that the scripting languages used inside Web browsers are really intended to solve specific types of problems, primarily the creation of richer and more interactive graphical user interfaces (GUIs). However, a scripting language might solve 80 percent of the problems encountered in client-side programming. Your problems might very well fit completely within that 80 percent, and since scripting languages can allow easier and faster development, you should probably consider a scripting language before looking at a more involved solution such as Java or ActiveX programming. The most commonly discussed browser scripting languages are JavaScript (which has nothing to do with Java; its named that way just to grab some of Javas marketing momentum), VBScript (which looks like Visual Basic), and Tcl/Tk, which comes from the popular cross-platform GUI-building language. There are others out there, and no doubt more in development. JavaScript is probably the most commonly supported. It comes built into both Netscape Navigator and the Microsoft Internet Explorer (IE). In addition, there are probably more JavaScript books available than there are for the other browser languages, and some tools automatically create pages using JavaScript. However, if youre already fluent in Visual Basic or Tcl/Tk, youll be more productive using those scripting languages rather than learning a new one. (Youll have your hands full dealing with the Web issues already.) 4.Java If a scripting language can solve 80 percent of the client-side programming problems, what about the other 20 percentthe “really hard stuff?” The most popular solution today is Java. Not only is it a powerful programming language built to be secure, cross-platform, and international, but Java is being continually extended to provide language features and libraries that elegantly handle problems that are difficult in traditional programming lan