The original release of the SRP HTTP Framework managed all configuration details within inserts and specific stored procedures. The unfortunately side-affect of doing this, especially the when the insert details were updated, was the need to recompile all stored procedures that are dependent on those inserts. As the library of web service routines grew, so did the task of recompiling all of these routines.
v1.0.1 introduced some changes by moving some of the configuration details into the SRP_HTTP_FRAMEWORK_SETUP record, which is stored in the SYSENV table. v2.0.0 completed this trend by having all of the remaining configurable details moved into SRP_HTTP_FRAMEWORK_SETUP. New application services (found in the HTTP_Services module) were created to access these settings, thus abstracting the method by which these details are maintained. For customers who are considering upgrading from v1.x to v2.0.0, this will require some minimal changes. Please refer to the Post-Installation Configuration article for information on configuring the SRP_HTTP_FRAMEWORK_SETUP record.
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. While these arguments were useful, we found that after building more web services, the meaning of the arguments would become unclear. For instance, what exactly is the different between the NextServiceHandler and the NextService? How did this relate to the current service being executed? What is contained in the NextURL? Now, obviously these are documented, but it still seemed as if these arguments could at times be confusing.
