M
Michael Jacobs
Guest
Building upon Edsel's suggestion, I see the /api service root in the path as not adding a lot of value. Having a version'd resource access looks like a good idea - but you may have other options than as a static value in the URL path. If the version was an URL option, your service handler code can easily dispatch to derived ABL classes where each child adds to the previous version's functionality (within a reasonable # of versions). To use one of Edsel's samples to give you another thought: /organization/{OrganizationId}/customer/ssn/{ssn}?vers=1 GET
Continue reading...
Continue reading...