Web Service (1)-Basic Concepts

Concepts:

1. soap is a lightweight protocol used to exchange structured information in a distributed and distributed manner. The core part of the SOAP specification is the message processing cabinet.

2. xmlweb Service uses the WSDL file to describe the software service provided by soap on the web, and registers it through UDDI. Because the Web service depends on HTTP. XML, SOAP. and WSDL and other industry standards, expand the functionality of applications on the Internet, so they are independent of programming languages, platforms, devices.

3. Differences between Web Service and. netremoting:

ASP. net XML Web serive Service provides a simple programming model based on message transmission, while. net remoting provides complex functions, including support for passing values or referencing younger brother objects, callback, and multi-object activation and lifecycle management.

4. ASP. NET Web Service supports three protocols for data exchange through Web Services: http. Get. Post with level soap

5: UDDI details can be viewed here: http://www.uddi.org

WSDL details can be viewed here: http://www.w3.org/TR/wsdl

Soap details can be viewed here: http://www.w3.org/TR/SOAP

I. Basic Introduction to a Web Service:

1. system. Web. Services namespace: This namespace contains services in Web services and must be known. In addition, different languages have different reputation methods.

Using system. Web. Services in C #

In VB, It is imports system. Web. Services.

2. webmethod attribute: The webmethod attribute is declarative code, which can be called through web using program logic. Different Languages have different reputation methods.

In C #, for example:

[Webmethod]

Public int funcname (int xxx)

In VB, for example:

<Webmethod> pulic function getxxx (XXX as integer) as integer

3. WebServices base class: Asp.net Web Services is part of Asp.net applications. Just as Asp.net applications have special configurations, ASP. NET WebService also has these features like sessions and data.

Note: Asp. NET page can access ASP.. NET web services can access the application state memory (like cache and session). Therefore, the items added to the application state memory or high-speed cache, this can be shared between pages and Web services. This allows resource reuse. For example, an e-commerce site can add inventory directories from the database to the application state memory at a time, and then ASP. Net pages and web services can share the data.

Five common (non-web call) attributes are added to the web service base class. We are familiar with the use of these attributes on the ASP. NET page.

1. Application ----- Application Status memory

2. Context -------- instance class transmitted during the entire request Period

3. Server ---------- session Status memory

4. User ----------- the user ID that sends the request (security features)