Like any development framework, the SRP HTTP Framework follows a specific architectural design to bring about helpful structure and order. Furthermore, since all of this is built around the ubiquitous world of the HTTP protocol, there are multiple architectures under consideration.
While we understand the desire to just jump in and write APIs* and web services*, we suggest that some effort be put into understanding the different architectures involved. Doing so will help ground you as you move forward. Many poor decisions are made largely due to the lack of grasping the technological "big picture" and system architecture. Our desire is that you get the most out of this framework, letting it do most of the work for you, rather than you trying hard to create unnecessarily workarounds that were only necessary because of ignorance:
* For the purpose of this documentation, APIs and web services are synonymous terms. They will be used interchangeably.
