The service-relative URI
- Last Updated: March 30, 2020
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
The service-relative URI must begin with a forward slash (/) followed by a unique service name.
Following the service name, you complete the path with a resource name that you will eventually map to a procedure or user-defined function. Choose a name that makes logical sense in the context of the service.
A developer's responsibility is to define the relative URI space for ease of use, extensibility, and versioning. You should not introduce elements of the AppServer procedure path and parameters when designing URIs.