I just read this from –
Beau Beuchamp at Medium.com
The following is a link to the full article supporting the argument that REST is an archaic technolgy that has been supplanted by better, more efficient services – including the author’s own invention – TIGER
Standards are fine if they work. But as use of the technology advances, often the “standard” starts to hold you back, and that is what REST is doing to the web.
- The following text and links are from the above article
TIGER: Easier Web Services That Work Better
TIGER is a name I coined for a loose standard of web services I developed about 12 years ago because I was tired of REST’s limitations and nonsense. TIGER is loosely based on a kind JSON-RPC (JSON remote procedure call) protocol that really just uses REST’s POST and/or GET verbs to send and receive data via the browser client. GET is used for quick grabs of data if you like, but POST is used almost exclusively to exchange data securely.
TIGER utilizes an easy-to-use “message pattern” to send and route data where it needs to go. Routing metadata are contained (co-mingled) within the “message” to the server.
As such, TIGER really needs only ONE endpoint.
Putting It All Together
I didn’t want to post a boatload of code within this article, so if you want to see TIGER Webservices in action, have a look at the TIGER Platform that uses these services on GitHub. Here are a few links:
-
A typical but simple plugin where a TIGER service is called:
Tiger/core.admin.cache.js at master · WebTigers/Tiger (github.com) -
The TIGER Webservice API Service Factory:
Tiger/ServiceFactory.php at master · WebTigers/Tiger (github.com)
>>> END of my Quotes from Beau Beauchamp’s article !
Last updated: