Re: Mixing sql and service program in IWS...
"Nadir Amra" <amra-r/[email protected]>
| Newsgroups | gmane.comp.systems.as400.web |
|---|---|
| Message-ID | <OFCBE67AD6.BDEAAA50-ON00258624.0018CAAB-86258624.0018F5BF@notes.na.collabserv.com> |
Kelly, that is a user beware scenario. The server will just choose one. "WEB400" <[email protected]> wrote on 11/17/2020 05:59:19 PM: > From: Kelly Cookson <KCookson-EAwJ3jYHSpVWk0Htik3J/[email protected]> > To: "Web Enabling the IBM i (AS/400 and iSeries)" <[email protected]> > Date: 11/17/2020 05:59 PM > Subject: Re: [WEB400] [EXTERNAL] Re: Mixing sql and service program in IWS... > Sent by: "WEB400" <[email protected]> > > Hi Nadir, > > 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, > -- This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list To post a message email: [email protected] To subscribe, unsubscribe, or change list options, visit: https://lists.midrange.com/mailman/listinfo/web400 or email: [email protected] Before posting, please take a moment to review the archives at https://archive.midrange.com/web400.