Re: [IBMiOSS] Node and Rest API's -- OPENSOURCE

× 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.

Subject: Re: [IBMiOSS] Node and Rest API's
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 30 Oct 2019 09:54:19 -0600
List-archive: <https://archive.midrange.com/opensource/>
List-help: <mailto:opensource-request@lists.midrange.com?subject=help>
List-id: IBMi Open Source Roundtable <opensource.lists.midrange.com>
List-post: <mailto:opensource@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/opensource>, <mailto:opensource-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/opensource>, <mailto:opensource-request@lists.midrange.com?subject=unsubscribe>

On Wed, Oct 30, 2019 at 9:11 AM Robert Rogerson <rogersonra@xxxxxxxxx>
wrote:

But about the two node servers. One to expose the web service (using
iToolkit) and one to consume the web service. Am I thinking about this
concept correctly?

Yes, what you are doing should work just fine. And you don't have to
consume in Node.js. The consumer could be Python, Ruby, Java, C++, even
curl + a shell script ...

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: [IBMiOSS] Node and Rest API's , Robert Rogerson

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.