west_way的博客

本书分成了三个部分：介绍性内容，第 I 部分 “Maven实战”，和第 II 部分 “Maven参考”。介绍性内容包括了两章：第 1 章介 绍 Apache Maven和第 2 章安 装和运行Maven。第 I 部分 “Maven实战”开发一些实际的例子，并一步步分析这些 例子的结构，同时循循善诱，详细解释，以此来解释Maven。如果你是Maven新手，应该 从第 I 部分 “Maven实战”开始阅读。第 II 部分 “Maven参考”更多的是参考而非 介绍，第 II 部分 “Maven参考”中的每一章集中讨论一个主题，并且会尽可能的深入 每个主题的细节。例如，第 II 部分 “Maven参考”中的第 17 章编 写插件一章通过 一些例子和表格解释如何编写插件。

java 并发编程实战 java 源码。

When performing database transactions in Java, Java objects are saved into a database as table rows. On the other hand, when retrieving data from a database, table rows are returned and converted to Java objects. The Java objects and table rows are two representations of the same piece of data. However, there are main differences between these two representations.

This book and its sequel—Inside Microsoft SQL Server 2008: T-SQL Programming—cover advanced T-SQL querying, query tuning, and programming in Microsoft SQL Server 2008. They are designed for experienced programmers and DBAs who need to write and optimize code in SQL Server 2008. For brevity, I’ll refer to the books as T-SQL Querying and T-SQL Programming, or just as these books.

Let me start with a few words about the lead author of this book, Itzik Ben-Gan. He is a mentor, consultant, presenter, teacher, and writer. All his roles have a common theme— Microsoft SQL Server programming. But wait—there’s even more: he is an MVP (officially “Microsoft Valued Professional,” but often interpreted as Most Valuable Programmer) and a close partner with many SQL Server developers in Redmond, Washington. The combination of these traits puts Itzik into a unique position when writing a book about SQL Server programming. He knows what works and what does not. He knows what performs and what does not. He knows what questions people ask when he is teaching. And he knows what people grasp easily and what they don’t when it comes to introducing more complex concepts of SQL Server programming.

■■Chapter 1: Performance Metrics..................................................................................1 ■■Chapter 2: Performance Measurement.........................................................................7 ■■Chapter 3: Type Internals...........................................................................................61 ■■Chapter 4: Garbage Collection....................................................................................91 ■■Chapter 5: Collections and Generics.........................................................................145 ■■Chapter 6: Concurrency and Parallelism..................................................................173 ■■Chapter 7: Networking, I/O, and Serialization..........................................................215 ■■Chapter 8: Unsafe Code and Interoperability............................................................235 ■■Chapter 9: Algorithm Optimization...........................................................................259 ■■Chapter 10: Performance Patterns...........................................................................277 ■■Chapter 11: Web Application Performance...............................................................305

Progressive Disclosure is a concept in User Interface Design which advocates only presenting to the user the information they need when they need it. In many ways, the book you are reading right now is an example of this principle. In fact, it is quite likely that this book wouldn’t have “worked” a mere seven years ago. For you see, the programming world was quite a different place when RESTful Web Services, the predecessor of this book, was written. At that time, the term “REST” was was rarely used. And when it was used it was often misapplied, and widely misunderstood. This was the case despite the fact that the standards upon which REST is based, namely HTTP and HTML, were developed and became IETF and W3C standards in roughly their current form in the second half of the 1990s. Roy Fielding’s thesis paper in which he introduced the term REST and on which this book was based was itself published in 2000.

Well, here we are again. Who would’ve thought? Oh, I know—I would’ve thought! When you sign up for marriage, you really are living Groundhog Day. If you haven’t seen that movie, watch it, because you will suddenly see why you have to make the same mistakes over and over again. In this case, when Jeff said he wouldn’t write another book, I knew it was the empty promise of an addict. Jeff cannot not write another book. Just today, we were discussing another book he is absolutely not going to write (except that there is already a chapter in progress). It is coded in his DNA. A thoroughbred is born to run and Jeff is born to write.

In the years since the first release of the .NET Framework, Microsoft has provided a variety of approaches for building service-oriented applications. Starting back in 2002 with the original release of .NET, a developer could fairly easily create an ASP.NET ASMX-based XML web service that allowed other .NET and non-.NET clients to call it. Those web services implemented various versions of SOAP, but were only available for use over HTTP. In addition to web services, the 1.0 release of .NET provided support for Remoting. This allowed developers to write services that weren’t necessarily tied to the HTTP protocol. Similar to ASMX-based web services, .NET Remoting essentially provides object activation and session context for client-initiated method calls. The caller uses a proxy object to invoke methods, and the .NET runtime handles serialization and marshaling of data between the client’s proxy object and the server’s activated service object.

Like many great advances in our industry, the explicit concept of aspect-oriented programming (AOP) was developed at what is now known as PARC, a Xerox Company. Soon after, in 2001, the AspectJ extensions brought AOP to Java. Aspects have enjoyed a long history in the Java community, but for many .NET developers, aspects are still considered new and exotic. Even so, many .NET developers have been using them without knowing it.

The practice of enterprise application development has benefited from the emergence of many new enabling technologies. Multi-tiered object-oriented platforms, such as Java and .NET, have become commonplace. These new tools and technologies are capable of building powerful applications, but they are not easily implemented. Common failures in enterprise applications often occur because their developers do not understand the architectural lessons that experienced object developers have learned.

C# 语言规范 微软出品 C#（读作“See Sharp”）是一种简洁、现代、面向对象且类型安全的编程语言。C# 起源于 C 语言家族，因此，对于 C、C++ 和 Java 程序员，可以很快熟悉这种新的语言。C# 已经分别由 ECMA International 和 ISO/IEC 组织接受并确立了标准，它们分别是 ECMA-334 标准和 ISO/IEC 23270 标准。Microsoft 用于 .NET Framework 的 C# 编译器就是根据这两个标准实现的。

介绍C# IL 英文版 Introduction to Microsoft's IL IL Basics Selection and Repetition Keywords and Operators ……

C++ Primer 第四版 UNIX平台源代码，代码经g++ v3.2以上版本编译.

对于想将Java应用于实际项目中的程序员来说，本书是一本权威性的指导书籍。作者是Cay S.Horstmannn以及Cray Cornell