2009年3月22日 · S0, API has actually a broader meaning than just building web APIs. Now let's take a look at the REST Architecture to build APIs. REST which stands for Representational State Transfer is basically a way of building web APIs in a logical way, making them easy to consume for ourselves or for others.

2013年10月30日 · In the case of a REST API with a JSON payload, 400's are typically, and correctly I would say, used to indicate that the JSON is invalid in some way according to the API specification for the service. By that logic, both the scenarios you provided should be 400s. Imagine instead this were XML rather than JSON.

I've had these issues mainly during high traffic periods of my application. I reduced them by reducing payloads i.e. reducing arrays and objects to only what I need to send, making my server algorithms more efficient, and returning valid exceptions on bad requests.

2022年1月20日 · the api works on your request for a certain amount of time; the api invokes your app to give you the results, at the callback url address. So you can invoke the api and tell your user the request is "processing" or "acquired" for example, and then update the status when you receive the response from the api. Hope it makes sense. -G

2015年12月7日 · Simply put: In REST applications, each request must contain all of the information necessary to be understood by the server, rather than be dependent on the server remembering prior requests. Storing session state on the server violates the stateless constraint of the REST architecture. So the session state must be handled entirely by the client.

HTTP can be a mere transport, as with SOAP etc., but REST was based on the design of HTTP, so a REST API saves a lot of design work by sticking as close to HTTP-as-app as possible. REST could be done on raw TCP or on top of HTTP or any other protocol, but that's a lot of wheels to reinvent when HTTP-as-application is right there, ready to be used.

Well Rest obviously shares attributes of other architecture styles etc. it's not all novel and new. Also, soap and rest are not mutually exclusive. A restful service could do so with soap (from what I understand). I think the uniform interface though, is unique in that it is a constraint, a requirement of rest, unlike other architectural styles.

2010年10月5日 · REST is somewhat of a revival of old-school HTTP, where the actual HTTP verbs (commands) have semantic meaning. Til recently, apps that wanted to update stuff on the server would supply a form containing an 'action' variable and a bunch of data. The HTTP command would almost always be GET or POST, and would be almost irrelevant. (Though …

2016年12月29日 · REST is a highly scalable and cachable architecture that is ideal for designing APIs. Basic ideas behind REST - URL and headers should uniquely identify the resource, such that it can be cached. REST APIs should be stateless i.e. result of an API call shouldn't vary depending on the API calls preceding it.

2013年4月22日 · Your case: HTTP 400 is the right status code for your case from REST perspective as its syntactically incorrect to send sales_tax instead of tax, though its a valid JSON. This is normally enforced by most of the server side frameworks when mapping the JSON to objects. However, there are some REST implementations that ignore new key in JSON