2010年8月26日星期四

2010年8月16日星期一

Introduction to Data Concurrency in ADO.NET

http://msdn.microsoft.com/en-us/library/cs6hb8k4(VS.80).aspx

ADO.NET and Visual Studio use optimistic concurrency, because the data architecture is based on disconnected data. Therefore, you need to add business logic to resolve issues with optimistic concurrency.

ASP.NET Page Life Cycle Overview

http://msdn.microsoft.com/en-us/library/ms178472.aspx

HTTP Handlers and HTTP Modules Overview

http://msdn.microsoft.com/en-us/library/bb398986.aspx

An ASP.NET HTTP handler is the process (frequently referred to as the "endpoint") that runs in response to a request made to an ASP.NET Web application. The most common handler is an ASP.NET page handler that processes .aspx files. When users request an .aspx file, the request is processed by the page through the page handler. You can create your own HTTP handlers that render custom output to the browser.
An HTTP module is an assembly that is called on every request that is made to your application. HTTP modules are called as part of the ASP.NET request pipeline and have access to life-cycle events throughout the request. HTTP modules let you examine incoming and outgoing requests and take action based on the request.
Typical uses for custom HTTP handlers include the following:
o RSS feeds To create an RSS feed for a Web site, you can create a handler that emits RSS-formatted XML. You can then bind a file name extension such as .rss to the custom handler. When users send a request to your site that ends in .rss, ASP.NET calls your handler to process the request.
o Image server If you want a Web application to serve images in a variety of sizes, you can write a custom handler to resize images and then send them to the user as the handler's response.
Typical uses for HTTP modules include the following:
o Security Because you can examine incoming requests, an HTTP module can perform custom authentication or other security checks before the requested page, XML Web service, or handler is called. In Internet Information Services (IIS) 7.0 running in Integrated mode, you can extend forms authentication to all content types in an application.
o Statistics and logging Because HTTP modules are called on every request, you can gather request statistics and log information in a centralized module, instead of in individual pages.
o Custom headers or footers Because you can modify the outgoing response, you can insert content such as custom header information into every page or XML Web service response.

ASP.NET Application Life Cycle Overview

for IIS 5.0 and 6.0
http://msdn.microsoft.com/en-us/library/ms178473.aspx

for IIS 7.0
http://msdn.microsoft.com/en-us/library/bb470252.aspx

2010年8月12日星期四

What is WSDL?

WSDL stands for Web Services Description Language
WSDL is written in XML
WSDL is an XML document
WSDL is used to describe Web services
WSDL is also used to locate Web services
WSDL is a W3C recommendation

The main structure of a WSDL document looks like this:




definition of types........



definition of a message....



definition of a port.......



definition of a binding....




WSDL Ports
The element is the most important WSDL element.
It describes a web service, the operations that can be performed, and the messages that are involved.
The element can be compared to a function library (or a module, or a class) in a traditional programming language.

WSDL Messages
The element defines the data elements of an operation.
Each message can consist of one or more parts. The parts can be compared to the parameters of a function call in a traditional programming language.

WSDL Types
The element defines the data types that are used by the web service.
For maximum platform neutrality, WSDL uses XML Schema syntax to define data types.

WSDL Bindings
The element defines the message format and protocol details for each port.

WSDL Example
This is a simplified fraction of a WSDL document:














What is endpoint?

All communication with a Windows Communication Foundation (WCF) service occurs through the endpoints of the service. Endpoints provide clients access to the functionality offered by a WCF service.

You can define one or more endpoints for a service by using a combination of relative and absolute endpoint addresses, or if you do not define any service endpoints, the runtime provides some by default for you.

Each endpoint consists of four properties:

•An address that indicates where the endpoint can be found.
•A binding that specifies how a client can communicate with the endpoint.
•A contract that identifies the operations available.
•A set of behaviors that specify local implementation details of the endpoint.

You can specify the endpoint for a service either imperatively using code or declaratively through configuration.

http://msdn.microsoft.com/en-us/library/ms734786.aspx

What is Fine-grained Service? What is coarse-grained service?

http://articles.techrepublic.com.com/5100-10878_11-5064520.html
Fine-grained services might be services that provide a small amount of business-process usefulness, such as basic data access.

Slightly more coarse-grained services might provide rudimentary operations, which are valuable to system experts, but are not much value to a business-process expert.

Services of the most value to business experts are constructed from low-level services, components, and objects that are intelligently structured to meet specific business needs. These coarse-grained services can be created from one or more existing systems by defining and exposing interfaces that meet business-process requirements.

Services as composite interfaces
Using coarse-grained interfaces, a system of services controls access to the objects referenced by each service. While each service may be implemented as an abstraction on a group of finer-grained objects, the objects themselves can be hidden from public access. Each service can be implemented by grouping objects, components, and fine-grained services, and exposing them as a single unit through the use of facades or interfaces