Version History

2.0.0

Major changes to improve the way RESTful web services process each segment in the URL:
- Changes to the HTTP_Services module:
  - Update the GetResponse service to use the GetResponseStatus service to populate the response body if there is no body already generated by a service.
  - Add GetFullEndPointURL service to provide a way of getting the URL sent by the client.
  - Update argument signatures for the RunHTTPService to be simpler and more intuitive.
- Refactor the HTTP_Service_Setup insert to be much cleaner and with fewer lines of code.
Add support for standard and developer customized HTTP response status codes:
- Create new configuration record in the SYSENV table: SRP_HTTP_FRAMEWORK_HTTP_STATUS_CODES.
- Update the GetResponseStatus service in the HTTP_Services module to use the SRP_HTTP_FRAMEWORK_HTTP_STATUS_CODES configuration record.
Add the following configuration options to SRP_HTTP_FRAMEWORK_SETUP:
- Entry Point Service
- Add GetEntryPointService to the HTTP_MCP controller.
Refactor various core routines to work with the previous changes:
- HTTP_Entry_Point_Services
- HTTP_Users_Services
- HTTP_Contacts_Services

Add the following configuration options to SRP_HTTP_FRAMEWORK_SETUP:
- Enable Authentication Flag
- Realm Value
Add the following services to the HTTP_Services module:
- GetHomeURL
- GetAPIURL
- GetCapturePath
- GetEnableAuthenticationFlag
- GetRealmValue
Update the HTTP_Authentication_Services helper to use the GetEnableAuthenticationFlag and GetRealmValue services. These services replaced hard-coded values.
Update the HTTP_MCP controller to use the GetCapturePath service. This replaced the Xlate.
Update the HTTP_Service_Setup insert to use the GetHomeURL and GetAPIURL services. These services replaced Xlated values.

Create two configuration records in the SYSENV table:
- SRP_HTTP_FRAMEWORK_VERSION - Stores the current version and build of the SRP HTTP Framework product.
- SRP_HTTP_FRAMEWORK_SETUP - Stores the Home URL, API URL, and Capture Path information.
Update the HTTP_Service_Setup insert to anticipate OECGI requests wherein the Script Name URL also exists within the Path Info URL (e.g., Microsoft IIS). This fixes a problem wherein the wrong service was being identified, especially in the Entry Point Service.
Update the HTTP_Service_Setup insert to assign the HomeURL$ and APIURL$ equates with the values stored in the SRP_HTTP_FRAMEWORK_SETUP record rather than being hard-coded. This eliminates the need to recompile HTTP service modules whenever the URL paths are changed.
Update the HTTP_Services module by adding a new service called GetVersion. This returns the information stored in the SRP_HTTP_FRAMEWORK_VERSION record.
Update the HTTP_MCP controller to use the capture path stored in the SRP_HTTP_FRAMEWORK_SETUP record. This eliminates the need to update the hard-coded path in HTTP_MCP and recompile.