On Dec 21, 2024, at 1:53 PM, Binyamin Dissen <[email protected]> wrote:
I have been looking at REST and do not see how it is different than a set of HTTP transactions. What am I missing? I know I’m late to this (just getting back from holidays) but, from Wikipedia (https://en.wikipedia.org/wiki/REST): “REST (Representational State Transfer) is a software architectural style that was created to guide the design and development of the architecture for the World Wide Web. REST defines a set of constraints for how the architecture of a distributed, Internet-scale hypermedia system, such as the Web, should behave.” So in one sense, REST is the theory and HTTP is the implementation. However, it’s quite possible to use HTTP methods in ways that are not fully consistent with the REST architectural style. When someone claims to have a REST API, they’re implicitly claiming, however accurately, that they are following the REST principles. I think, though, when most people talk about REST APIs they mean “using HTTP where the client isn’t a human in front of a browser.” -- Curtis Pew Enterprise Technology, Campus IT Infrastructure and Services, Mainframe and Administrative Systems The University of Texas at Austin [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
