× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Kelly, that is a user beware scenario. The server will just choose one.

"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 11/17/2020 05:59:19
PM:

From: Kelly Cookson <KCookson@xxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
<web400@xxxxxxxxxxxxxxxxxx>
Date: 11/17/2020 05:59 PM
Subject: Re: [WEB400] [EXTERNAL] Re: Mixing sql and service program in
IWS...
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>

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,





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.