Page History

...

In the SRP HTTP Framework module, the entry point, URL segments, and the end point are managed by separate HTTP services. Segments that are resource identifiers are handled by the preceding HTTP service. Thus, the service that is written to handle the customers segment will also look ahead to see if a specific customer (e.g., 5678) has been included. If so, it will process the request accordingly. A default entry point routine is HTTP_Entry_Point_Services, is included with SRP HTTP Framework. As a design standard, the name of the BASIC+ routine that acts as a web service for a given segment follows this pattern: HTTP_<URLSegment>_Services. Hence, the customers segment would be likely be managed by HTTP_Customers_Services.

Because customers is the first segment that follows the entry point, it would be the responsibility of HTTP_Entry_Point_Services to   to pass the HTTP request onto HTTP_Customers_Services (and so on, as the URL path continues). The end point is where the HTTP response is generated. When the end point is a resource type, the service typically returns a collection (or list) of available resource identifiers (or Key IDs) that belong to the specific resource. If the end point is a specific resource identifier then the data corresponding to this resource is returned. In the above URL, phone is a resource type and work is the resource identifier.

...