英语原文共 15 页 译文共 14 页

英语原文共 16 页， 英语原文共 17 页，资料编号：[142613]，资料为PDF文档或Word文档，PDF文档可免费转换为Word

Android Application Fundamentals Android applications are written in the Java programming language. The Android SDK tools compile the code—along with any data and resource files—into an Android package, an archive file with an .apk suffix. All the code in a single .apk file is considered to be one application and is the file that Android-powered devices use to install the application. Once installed on a device, each Android application lives in its own security sandbox: The Android operating system is a multi-user Linux system in which each application is a different user. By default, the system assigns each application a unique Linux user ID (the ID is used only by the system and is unknown to the application). The system sets permissions for all the files in an application so that only the user ID assigned to that application can access them. Each process has its own virtual machine (VM), so an applications code runs in isolation from other applications.

Core Javareg; Volume II—Advanced Features Cay S. Horstmann Gary Cornell The preface of the book Essential XML by Don Box et al. (Addison-Wesley, 2000) states only half-jokingly: “The Extensible.Markup Language (XML) has replaced Java, Design Patterns, and Object Technology as the software industryrsquo;s solution to world hunger.” Indeed, as you will see in this chapter, XML is a very useful technology for describing structured information. XML tools make it easy to process and transform that information. However, XML is not a silver bullet. You need domain-specific standards and code libraries to use it effectively. Moreover, far from making Java technology obsolete, XML works very well with Java. Since the late 1990s, IBM, Apache, and others have been instrumental in producing high-quality Java libraries for XML processing. Many of these libraries have now been integrated into the Java platform. This chapter introduces XML and covers the XML features of the J

英语原文共 10 页， 英语译文共 17 页， 资料编号：[607501]，资料为PDF文档或Word文档，PDF文档可免费转换为Word

英语原文共 9 页， 英语译文共 9 页， 资料编号：[609431]，资料为PDF文档或Word文档，PDF文档可免费转换为Word

英语原文共 53 页， 数字签名：背景和定义 1.1数字签名方案：一个快速简介 严格意义上，一个数字签名方案提供的加密模拟手写签名，事实上，提供了更强大的安全保障。数字签名作为一个强大的工具，如法律上现在公认的具有约束力在许多国家;它们可以用于证明合同或公证文件，为个人或公司的认证，并作为一个以上组件复杂的协议。数字签名也使公共密钥的安全分发和传输，因此，在一个非常现实的意义，作为所有的基础 公共密钥加密。 ifiers。 （我们这里的讨论将是比较正规的，我们推迟正式定义直到后来）签名人开始通过运行一些关键的生成算法产生一对密钥（PK，SK），其中PK将被称为签名者的公钥 - 原因次也被称为它的秘密密钥）。然后，签名人宣扬其公钥，我们将假设任何潜在验证是在拥有（或可以获得）

英语原文共 16 页 目 录 一、web编程.....................................................................................................................................................................17 二、概述.............................................................................................................................................................................19 三、JavaScript的连续性....................................................................................................................................................20 四、JavaScript的子语言....................................................................................................................................................24 五、执行控制.....................................................................................................................................................................25 六、评

英语原文共 20 页 英语原文共 20 页资料编号：[3461]

1.4.1. Dependency Injection Dependency injection (DI) is a process whereby objects define their dependencies (that is, the other objects with which they work) only through constructor arguments, arguments to a factory method, or properties that are set on the object instance after it is constructed or returned from a factory method. The container then injects those dependencies when it creates the bean. This process is fundamentally the inverse (hence the name, Inversion of Control) of the bean itself controlling the instantiation or location of its dependencies on its own by using direct construction of classes or the Service Locator pattern. Code is cleaner with the DI principle, and decoupling is more effective when objects are provided with their dependencies. The object does not look up its dependencies and does not know the location or class of the dependencies. As a result, your classes become easier to test, particularly when the dependencies are on interfaces or abs