Chapter 1
The book starts by examining the forces that come to bear on the design of a distributed application. This chapter is high level, but it sets the stage for the specific technical discussions that follow by taking a look at what influences the decisions you need to make about the technology choices available for a distributed application. There are many resources available to help you with specific technologies, in isolation from the rest of your application.
Chapter 2
Here we step out of the world of ASP.NET Web Form processing and examine the larger infrastructure that this request processing exists within. This is the same pipeline used by Web Services, and it is the same pipeline that will be used by Windows Communication Foundation (WCF). It is also built for extensibility, meaning you can do your own type of request processing by customizing this pipeline.
Chapter 3
This chapter focuses solely on the System.Web.UI.Page class, the fundamental type for Web Form programming. Here we peel the covers back on this type, and examine its internal structure: the control tree, which is fundamental to all ASPX request processing. We'll also show you some changes that have been made to this model in ASP.NET 2.0, including a new compilation model, new deployment options, and some new events available in the lifetime of the page-request processing.
Chapter 4
This chapter focuses on some of the more subtle communication that occurs between the web server and the web browser in ASP.NET request processing.We'll look specifically at the ViewState, enhancements to the scripting model that ease the generation of client-side JavaScript, and an amazing new feature that allows for out-of-band asynchronous callbacks from a web browser to the web server.
Chapter 5
This chapter focuses on security, the "vertical slice" of any distributed application. Here you'll see how to keep assemblies secure and how you can leverage encryption in the .NET Framework, as well as some new security features in ASP.NET 2.0.
Chapter 6
This chapter is on Web Services in the .NET Framework.We'll take a look at why you would want to use Web Services, we'll examine them from a vendor-neutral perspective to see how they provide for excellent cross-platform interoperability, and then we'll delve into some of the new features for Web Services that are built into version 2.0 of the .NET Framework. We'll wrap this chapter up with a quick look at Web Service Enhancements, an add-on package of functionality available from Microsoft.
Chapter 7
This chapter is about COM+. We enumerate its features and look specifically at what steps you must take with .NET types for them to function in the COM+ environment.
Chapter 8
This chapter focuses on processes, hosts, and marshaling. These topics are seldom discussed under a single banner, and the decisions you make regarding them affect every distributed application. We'll examine some of the options available for hosting applications and also some of the options for communicating across the different processes. Through the course of this discussion, we'll examine Message Queuing in some detail, as well.
Chapter 9
This chapter provides a brief introduction of Windows Communication Foundation, Microsoft's next-generation messaging stack that sets out to unify (or at least unite) MSMQ, COM+, Remoting, and Web Services.
Chapter 10
The third part of the book starts with an overview of ADO.NET, with a focus not so much on the "hows" of using a managed provider for data access, but rather on when to use different types and techniques and some best practices for each scenario.
Chapter 11
Several features of the Framework are designed for the data access layer, yet they don't directly pertain to managed providers. We'll examine some of these key services here, including data source controls, database-dependent cache entries, and the data access layer application block.
Chapter 12
The next version of the Framework introduces a more elaborate transaction model, enabling you to have a transaction manage work that gets done in memory, so it can be rolled back the same way transactional database work can be.We'll examine this and see how a transaction can start as you make modifications to business objects, and then be promoted to do database work, and get promoted again if the transaction becomes distributed across databases. We'll also show you how to implement your own resource manager, which can do work that will participate in these transactions.
Download:
Link_1
0 comments:
Posting Komentar