REST is the underlying architectural principle of the web. The amazing thing about the web is the fact that clients (browsers) and servers can interact in complex ways without the client knowing anything beforehand about the server and the resources it hosts.
The key constraint is that the server and client must both agree on the media used, which in the case of the web is HTML.An API that adheres to the principles of REST does not require the client to know anything about the structure of the API. Rather, the server needs to provide whatever information the client needs to interact with the service. An HTML form is an example of this: The server specifies the location of the resource, and the required fields. The browser doesn't know in advance where to submit the information, and it doesn't know in advance what information to submit. Both forms of information are entirely supplied by the server. (This principle is called HATEOAS.)So, how does this apply to HTTP, and how can it be implemented in practice? HTTP is oriented around verbs and resources.
The two verbs in mainstream usage are GET and POST, which I think everyone will recognize. However, the HTTP standard defines several others such as PUT and DELETE. These verbs are then applied to resources, according to the instructions provided by the server.We provide RESP API module for uHotelBooking script.
There are site admins or hotel owners who can access protected site data.
Single PHP file, easy to deploy.
Very little code, easy to adapt and maintain
Streaming data, low memory footprint
Supports POST variables as input
Supports a JSON object as input
Condensed JSON ouput: first row contains field names
Sanitize and validate input using callbacks
Permission system for databases, tables, columns and records
Multi-tenant database layouts are supported
Both JSONP and CORS support for cross-domain requests
Combined requests with support for multiple table names
A regular license allows an item to be used in one project for either personal or commercial use by you or on behalf of a client. The item cannot be offered for resale either on its own or as part of a project. Distribution of source files is not permitted.
An extended license allows an item to be used in unlimited projects for either personal or commercial use. The item cannot be offered for resale "as-is". It is allowed to distribute/sublicense the source files as part of a larger project.