Is webservice an implementation of RPC?

Title. WebService is one of the RPC??

Reply content:

Title. WebService is one of the RPC??

Strictly speaking, not a hierarchy of concepts.
The generalized RPC and MQ side-by-side, belong to the two major ways of interaction between systems. It can be thought that webservice belongs to the generalized RPC, and of course there are xml-rpc and JSON-RPC.

If it's xml-rpc, you can count webservice, and it's not clear.

As you can see, I understand that RPC is a remote process call, and whether you're using the HTTP protocol or the socket protocol, the ability to invoke a remotely defined interface can be called RPC.

There is little interest in such issues, but I have read an article like this:

In 1998, a bull-man Dave Winer, a small company named Userland, designed Xml-rpc, which was immediately favored by Microsoft, because it was in the XML. This xml-rpc was originally called soap, until Microsoft saw it and sent people to work together. Soon they finished the earliest implementations and were renamed XML-RPC.
OK now the implementation of no problem, but to promote, or standardized a better, so Microsoft to IBM, Oracle, Sun, Apple, Netscape and so on to look for us to standardize it together, so that we can all together with it to make money, so soap was formed.
But you know, these big manufacturers to set standards that is the Huaiguitai ah, how can Microsoft treat the cheap so kindly to other people to share it? So the SOAP standard includes content that allows private extensions in addition to a tiny, generic part. and Microsoft in this process, has begun to do this part of the content, so soap just came out, Microsoft has been the first to the other people launched a mature webservice products. This is the webservice that you see later in. NET 1.0.

Excerpt from: Andot's Blog

WebService can be understood as a way to implement RPC, which transmits data in the form of XML.

