On Sun, Jan 23, 2022 at 9:14 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:

Using an Apache server instance works well and is very fast.
Very simple to setup and effective using it for REST architecture, especially in those shops with old school rpg programmers.

Help your staff out by writing a simple “landing” program that offloads the request from the server then looks up an appropriate native rpg pgm to call passing it two parms. 1) in = request json 2) out = response json.

Your team can write simple rpg pgms that accept this request parm, parse it with sql json function, then produce the response packing it back up with sql json functions.

Your devs never have to interface with any http stuff at all. They just need to learn how to work with json. And between data-into, YAJL, sql, they will get by just fine. My suggestion is to use the sql functions.

I would choose this over IWS over ILEAstic any day.

I know basically nothing about Apache, IWS, or ILEastic, so I'm
neither a fan nor detractor of any of those.

But, given that IWS and ILEastic seem to have gone out of their way to
allow you to sidestep Apache, clearly some people thought they could
provide significant value over using Apache, particularly for RPG

So what, in your opinion, makes Apache so much better than the other
two? Is it easier to write the "simple landing program" against Apache
versus against IWS or ILEastic? Or are you saying that (Apache + your
helper interface) is so much better than (IWS + no helper interface)
which in turn is better than (ILEastic + no helper interface)?

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2022 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.