The web service r the web based applications that dynamically interact with other web applications using open standards that include XML, UDDI n SOAP.
A web service is a collection of protocols n standards used for exchanging data b/w applications or systems s/w applications written on various programming languages n running on various platforms can use WS to exchange data over the internet in a manner similar to inter process comm. On a single computer. This interoperability (eg: b/w Java n python or windows n Linux applications) is due to the use of open standards.
Web Service (WS) are meant to expose functionality of a server to other applications
As long as client application has support for SOAP, it can call remote WS n return data for it.
Advantages:
1. WebServices are small units of code designed to handle a limited set of tasks
Eg : small program designed to supply other applications with the latest stock exchange process.
2. Web Services uses XML based communicating protocols
3. Web Services are independent of OS n programming languages
Since they use XML based protocols to communicate with other systems, Web Services are independent
Applications calling a Web Services always send its request using XML, n gets its answer returned as XML. Soothe calling applications will never concerned abt the OS or the programming language running on the other computer
4. Web Service connect people, systems and devices
5. Easier to use existing services
6. easier to distribute info to more consumers.
7. Rapid Development..
With context to .Net
--WS promise to bring info into your applications from the internet
--The .net framework introduces WS as a integral part of the architecture.
--the .net framework abstracts most of the internet logic that handles the remoting details of the methods calls over the wire n vs.net builds support for web services directly into the development environment.
--WS aim is to provide a RPC interface for client applications to call class methods on the server side.
-- In order to create a WS , u create a class method with standard input n output parameters n make this class n the specific methods as exposable over the Net
--WS are meant to expose functionality of a server to other applications
--As long as client application has support for SOAP it can call the remote WS n return data for it.
--SOAP is the protocol that is responsible for routing the RPC message from the client to the server n returning the result back to the client application. SOAP is based on XML.
The 3 major components that make up a WS:
1. The WS on the server side
2. The client application calling the WS via a web reference
3. A WSDL WS description that describes the functionality of the Ws.
WSDL:
When u creates a WS, we automatically get support for WSDL schema.
A WSDL file describes all the methods n method signatures as well as the namespace n the handling URL for the WS in an XML document.
--A WS in .Net consists of .ASMX page that either contains a class that provides the web service functionality or references a specific external class
--classes are standard .Net classes and the difference is that every method is prefixed with [wed method] attribute
--Once the .ASMX page has been created, the WS is ready for accessing over the web.
--.Net Ws that run over HTTP, can be called in 3 diff ways
1. HTTP GET Operation:
We can pass parameters to a WS by calling the ASMX pahe with querystring parameters ex: webDemo.asmx/MethodName?Param1=value
2. HTTP Post Operation
Here, the parameters are passed as standard URL encoded form variables
Ex: WebDemo.asmx/MethodName
3. SOAP
This is the proper way to call a WS in .NET n its also the way tht .NET uses internally to call WS
,%@ Webservice language=”c#”
A web service is a collection of protocols n standards used for exchanging data b/w applications or systems s/w applications written on various programming languages n running on various platforms can use WS to exchange data over the internet in a manner similar to inter process comm. On a single computer. This interoperability (eg: b/w Java n python or windows n Linux applications) is due to the use of open standards.
Web Service (WS) are meant to expose functionality of a server to other applications
As long as client application has support for SOAP, it can call remote WS n return data for it.
Advantages:
1. WebServices are small units of code designed to handle a limited set of tasks
Eg : small program designed to supply other applications with the latest stock exchange process.
2. Web Services uses XML based communicating protocols
3. Web Services are independent of OS n programming languages
Since they use XML based protocols to communicate with other systems, Web Services are independent
Applications calling a Web Services always send its request using XML, n gets its answer returned as XML. Soothe calling applications will never concerned abt the OS or the programming language running on the other computer
4. Web Service connect people, systems and devices
5. Easier to use existing services
6. easier to distribute info to more consumers.
7. Rapid Development..
With context to .Net
--WS promise to bring info into your applications from the internet
--The .net framework introduces WS as a integral part of the architecture.
--the .net framework abstracts most of the internet logic that handles the remoting details of the methods calls over the wire n vs.net builds support for web services directly into the development environment.
--WS aim is to provide a RPC interface for client applications to call class methods on the server side.
-- In order to create a WS , u create a class method with standard input n output parameters n make this class n the specific methods as exposable over the Net
--WS are meant to expose functionality of a server to other applications
--As long as client application has support for SOAP it can call the remote WS n return data for it.
--SOAP is the protocol that is responsible for routing the RPC message from the client to the server n returning the result back to the client application. SOAP is based on XML.
The 3 major components that make up a WS:
1. The WS on the server side
2. The client application calling the WS via a web reference
3. A WSDL WS description that describes the functionality of the Ws.
WSDL:
When u creates a WS, we automatically get support for WSDL schema.
A WSDL file describes all the methods n method signatures as well as the namespace n the handling URL for the WS in an XML document.
--A WS in .Net consists of .ASMX page that either contains a class that provides the web service functionality or references a specific external class
--classes are standard .Net classes and the difference is that every method is prefixed with [wed method] attribute
--Once the .ASMX page has been created, the WS is ready for accessing over the web.
--.Net Ws that run over HTTP, can be called in 3 diff ways
1. HTTP GET Operation:
We can pass parameters to a WS by calling the ASMX pahe with querystring parameters ex: webDemo.asmx/MethodName?Param1=value
2. HTTP Post Operation
Here, the parameters are passed as standard URL encoded form variables
Ex: WebDemo.asmx/MethodName
3. SOAP
This is the proper way to call a WS in .NET n its also the way tht .NET uses internally to call WS
,%@ Webservice language=”c#”
