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



Comments in-line Booth.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 10, 2019, at 2:00 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

I would make the case _/for/_ IWs in an RPG environment.

Reason 1 is that experienced RPG programmers will be up to speed and serving/consuming json data in days, not weeks. Existing shops with existing staff will not go through the angst of malformed files, missing steps, and testing that isn't thorough.

I have found that most RPGers pick up on how to create (for consuming I'd use HTTPAPI) web services with RPG (for example) more easily than they learn to produce web pages. In terms of configuration it can get more complicated in terms of Apache configuration if someone else is dictating what the web service interface needs to look like. On the other hand, even using the IWS wizard requires that you understand a lot of rather arcane terminology which the manuals describe in "Unixese". And I _know_ you had a lot of problems with that because I watched your posts here on the topic.


Reason 2 is that experienced PHP, node, and Python hires can be brought in and be useful from Day 4 and not be forced to understand RPG before pulling their full weight.

That surely is a reason to use Python/PHP/whatever and not IWS


Reason 3 is that it helps build the wall between sensitive data and a world-that-doesn't-need-to-know-the -details.

Which is true of any web service no matter what drives it.


.

On 7/10/2019 12:09 PM, Jon Paris wrote:
REST for sure. And personally I would not use IWS for a multitude of reasons. I love it for proof of concept stuff but I'd rather "roll my own" using PHP, node, Python or RPG.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.



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.