/
Versioning
Versioning
Versioning in LMFS Web Services is accomplished through a number of conventions in our implementation.
- New parameters that are introduced will be optional parameters. Any validation that is needed with the new parameter will return an error in the typical error code format. (Note that these types of changes will be available in the staging lab well in advance of it being deployed to operations.)
- New return values in the XML response for SOAP or the JSON string for REST will be controlled via the versionRequested parameter. The versionRequested value is in the form of a date (YYYYMMDD). When versionRequested is supplied, it restricts the set of return values to those that were defined as of that date. If versionRequested is not supplied, it defaults to the initial (oldest) version of the web service response. Note that the online documentation provides information on what versionRequested maps to particular return values.
- New functions will be offered as new web service requests so that previously offered functionality remains available.
, multiple selections available,
Related content
11.4 Leidos Web Service Release Notes
11.4 Leidos Web Service Release Notes
More like this
11.5 Leidos Web Service Release Notes
11.5 Leidos Web Service Release Notes
More like this
11.3 Leidos Web Service Release Notes and Advance Notice for 11.4
11.3 Leidos Web Service Release Notes and Advance Notice for 11.4
More like this
PIREP Submission
PIREP Submission
More like this
Lab or Operations - Notification of Maintenance or Disruption in Service
Lab or Operations - Notification of Maintenance or Disruption in Service
More like this
Authentication and Authorization
Authentication and Authorization
More like this