Page History

The original release of the SRP HTTP Framework managed all configuration details within inserts and specific stored procedures. The unfortunate side-affect of doing this, especially the when the configuration details within the insert details were updated, was the need to recompile all stored procedures that are were dependent on those inserts. As the library of web service routines grew, so did the task of recompiling all of these routines.

...

The other big change has to do with the way the RunHTTPService application service is called. The original version of this service had three arguments: NextServiceHandler, NextService, and NextURL. Over time it became apparent that these could be reduced to just two arguments, which are now named HTTPService and RemainingURL. This allowed us to refactor the HTTP_Service_Setup insert, reducing its line count by half, and making it much simpler to follow.

This invariable invariably affected the argument signature and internal variables used by the actual web service routines. Previously, these routines used a generic service signature, even though only the first two arguments were ever populated. Now they only accept one argument, which is named RemainingURL to correspond with the same argument being passed to the RunHTTPService application service. The new sample HTTP service routines (HTTP_Entry_Point_Services, HTTP_Users_Services, and HTTP_Contact_Services) have updated comments comment blocks that clearly documents document all of the variables that are populated by the HTTP_Service_Setup insert. This will help the developer understand what information is available so that API logic can be written much easier.