The RPC is Remote Procedure Call. It is the method used for calling a procedure or function available on any remote computer on the web.

XML-RPC refers to a simple protocol used to perform RPCs by using XML messaging. It is an excellent tool for connecting different environments and also establishing connections between wide varieties of computers.

The BEEP stands for Blocks Extensible Exchange Protocol. BEEP is an alternative to HTTP and FTP. BEEP is determined as building new protocols for the variety of applications such as instant messaging, network management, file transfer. It is termed as new Internet Engineering Task Force (IETF) which is layered directly over TCP.

Some of the Build-in features of BEEP protocol are listed below:

• Authentication
• Security
• Error handling
• Initial Handshake Protocol

The requirement for accessing web services from any application is that should support XML-based request and response. Hence there is no need to install any app for accessing web services.

The UDDI uses the language known as WSDL (Web Service Description Language).

Enlisted below are some common HTTP methods along with their functions that are supported by RESTful web services.

• GET: Read-only access to the resource.
• PUT: Creation of new resource.
• DELETE: Removal of a resource.
• POST: Update of an existing resource.
• OPTIONS: Get supported operations on the resource.
• HEAD: Returns HTTP header only, nobody.

These are the steps involved in accessing a web service:

1. Client application bundled the information and into a SOAP message.
2. SOAP message sends to the server as a body of Hyper-Text markup language using POST method.
3. Web service unpacks the SOAP message and converts it into a command understandable by the application.
4. Application processes the information and in turn bundled the info and send it back to the client as a SOAP message.
5. A Client then unpacks the SOAP message to obtain the results.

Communication protocol refers to the protocols which were used to transmit information over the web. By using Transport protocols, applications from the different background can quickly communicate with each other without knowing the inside functioning of the various systems. HTTP (Hyper-Text Transfer Protocol) can be used to implement a SOAP message whereas FTP (File Transfer Protocol) can be used as the reliable transport mechanism. SMTP and BEEP can also be used for transport mechanism.

SOAP message is not tied to any protocol. It can use any of the open Transport protocol.

The terms "Platform independent" and "Diverse Application" were related to each other because XML-RPC uses HTTP for transporting SOAP messages over the web. The HTTP is a universal standard protocol for exchanging information on the Web. Hence, it leads to Cross Platform support/ Platform independent. So because it is Platform independent, it leads to the diverse application capable of accessing the web services.

The role of a Web Service provider is to implement web service and make it available to the web service requestor/ consumer.

The role of Web Service Requestor / Consumer is to utilize the pre-existing web service provided by the Web Service Provider/ Publisher. Web Service Requestor/ Consumer request the Web Service provider for the information by sending a SOAP message to the Web Service provider. Then in-Turn Web Service Publisher sends the requested information back to the requestor in the form of a SOAP message.