Rest services for iOS-standby

The three most important features of restful services are * * stateless * * (statelessness), * * Unified resource Positioning * * (Uniform Resource identification) and * * cacheable * * (cacheability).

RESTful services are always stateless. Each time the API call is considered a new request, the server does not log the client context. The client needs to maintain the state of the server, including but not limited to the cache server Response (response) and the login access token (login to access tokens).

The resource positioning of restful services is implemented through URLs. Rest does not use the resource ID as a parameter, but instead uses it as part of the URL. For example, the Http://example.com/resource?id=1234REST service becomes http://example.com/resources/1234. In

RESTful services Use this approach for resource positioning and do not maintain client state, which allows clients to respond to the URL cache, just as the browser caches the page.

The response of a restful service is usually returned to the client in a uniform, mutually agreed-upon format, which allows for better decoupling of the client interface and the server interface. The client's iOS app communicates with a restful server using a mutually agreed data interchange format. So far, the most commonly used formats are XML and JSON. The next section discusses the differences between these formats and how to resolve them in your app.

I don't know much at the moment.

Rest services for iOS-standby