All geek questions in one place

Is XML-RPC poorly used as a protocol for publicly implementing an API?

I need to implement a web API for a project that I have been working on during this period. I read that there are many standard protocols for this: XML-RPC, SOAP, REST. XML-RPC seems to be one of the easiest to implement and use from what I've seen, but I haven't found anything about using it to implement the API. Instead, I found many tutorials on creating a REST API in PHP, for example. Is there any counter indication for using XML-RPC to implement a public web API?

In addition, in general, I could (sort of) define my own protocol for my API to simplify the work (i.e. accept only a GET request containing the parameters I needed): would it be so bad? Is the use of a standard protocol mandatory?

+3
source share
6 answers

If your application is very simple, then there is nothing wrong with just using GET requests and passing parameters. You do not need to use any standard like SOAP.

REST, , , - . , , , GET, PUT URL. , .

SOAP/XML-RPC - , , - XML () . , . , -, , .

, JSON . , -, javascript. HTTP GET, JSON.

+1

SOAP, .

, SOAP, , XML-RPC. XML-RPC.

SOAP XML-RPC, XML-RPC .

0

, , SOAP RESTful API , API, , .

, , , RESTful API. , , RESTful API , , , .

0

  • HTTP
  • XML RPC
  • SOAP

, , HTTP. ( ) XML RPC. , API . SOAP.

, XML-RPC . HTTP- POST ( , , - , , ) SOAP, .

"", JSON RPC XML RPC. JSON , .

0

, ( ), .

HTTP defines operations / actions / verbs that can be used. If you use this, you can provide a single interface that api users can invoke without having to learn your new plans.

This will allow you to get one of the useful limitations in REST .

0
source

Well. I had to make the magento android android application for the company and was confused between the three SOAP, REST and XML-RPC, ended up going with XML RPC - really awesome and simple: D

0
source

Source: https://habr.com/ru/post/1783017/

More articles:


All Articles