Option A: If I choose *not* to give each procedure a unique "URI path template for method," then I need to make sure that each procedure uses a different "HTTP request method." Only one procedure receives a GET request. Only one procedure receives a POST request, and so forth. The max number of procedures would be four (i.e., the number of drop down options for the "HTTP request method" box).
Option B: If I choose to give each procedure a unique "URI path template for method," then I can have each of the procedures use whatever "HTTP request method" that I want to assign them. I might have three procedures that all receive GET requests as long as each of the three procedures has a unique "URI path template for method" assigned. The max number of procedures is limited by considerations other than the number of drop down options for the "HTTP request method" box.
This is useful to know. There may be situations where I may not have a choice of which option to use. Good to know I can do both.
Senior Software Engineer II
Dot Foods, Inc.
1-217-773-4486 ext. 12676
From: WEB400 <web400-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Nadir Amra
Sent: Tuesday, November 17, 2020 10:33 PM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [WEB400] Mixing sql and service program in IWS...
Kelly, that is a user beware scenario. The server will just choose one.
This thread ...
Re: Mixing sql and service program in IWS..., (continued)
This mailing list archive is Copyright 1997-2020 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