SRP FrameWorks and the SRP HTTP Framework module both use an SOA approach toward programming that is used to assist with general programming and business solution tasks. Each stand-alone portion of logic is referred to as a service. To help with organization, services with a common general purpose are grouped into service modules (also known as service handlers). In OpenInsight, service modules are represented by stored procedures: HTTP_Services, Security_Services, etc. Within each service module are the respective services. Services are organized within service modules via label/return blocks.
Our SOA paradigm fits within the broader architecture known as Model-View-Controller (MVC). In this framework, a Model represents the database and business logic processes, a View represents the user interface (e.g., Form) and its respective event logic (e.g., Commuter Module), and a Controller represents the middleware that allows the Model and View to communicate with one another. Service Modules and their respective Services typically fall into the Model. Consequently, services should be designed carefully to avoid actions that belong to a View. For instance, this means a service designed for business logic should not invoke a UI. Likewise, View logic should not directly access the database. This requires discipline and an acceptance of the purpose for MVC based applications (of course, the inherent design of any web application enforces this architecture).
SRP FrameWorks uses one Controller, which is a stored procedure called MCP. The SRP HTTP Framework, however, needed a new controller so that it could handle HTTP requests and responses. This stored procedure is called HTTP_MCP. This was already referenced in the Introduction as the replacement to the RUN_OECGI_REQEUST listener.
