Rest is a way of doing things. There isn't a standard.
Actually, REST does have a standard. People just don't always use every aspect of the standard when they build "RESTful" web services.
REST, or Representational State Transfer, was invented by Roy Thomas Fielding. It was part of his dissertation (entitled "Architectural Styles and the Design of Network-based Software Architectures") at the University of California Irvine. He describes a specific set of characteristics as defining REST in his dissertation. And, since Fielding invented the concept of REST per se, one can reasonable say these characteristics are the standard of REST.
However, today the terms REST and RESTful are commonly applied to web services and web APIs that do not satisfy all the characteristics described by Fielding. That's okay by me. I'm not a purist, and I'm not the language police. But just be aware that REST had a definite origin and had a set of standard characteristics defined it when it originated.
Those interested can download a free copy of Fielding's dissertation here:
https://www.ics.uci.edu/~fielding/pubs/dissertation/fielding_dissertation.pdf
REST is discussed in Chapter 5, which starts on page 76. It's an academic/theoretical work, so don't expect a how-to manual. But it's not filled with too much jargon. I was able to get the main ideas after a couple of readings.
Thanks,
Kelly Cookson
Senior Software Engineer II
Dot Foods, Inc.
217-773-4486 ext. 12676
www.dotfoods.com<
http://www.dotfoods.com/>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.