I think you are emphasizing that things can be set up so different types of HTTP requests (GET, POST, PUT, DELETE) will execute different procedures in the IWS REST service without needing to add anything to the URI. That makes sense to me.
I was emphasizing that one does not need to have a one-to-one correspondence between types HTTP requests and procedures within the IWS REST service. For example, it is possible to have multiple procedures within the same IWS REST service all use the HTTP GET request.
But now I do have a question:
Can you have 3 procedures *within the same IWS REST service* all use the GET HTTP request method without specifying a unique URI path template for each of those three procedures?
If you select GET as the "HTTP request method" for three procedures, but you do not specify a unique "URI path template for method" for each of those three procedures, then how would the service know which procedure to execute when it receives an HTTP GET request?
Thanks,
Kelly Cookson
Senior Software Engineer II
Dot Foods, Inc.
1-217-773-4486 ext. 12676
www.dotfoods.com
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: [EXTERNAL] Re: Mixing sql and service program in IWS..., (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.